The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/4d48c89a785d28e8046042687bddc1b5789f6d5c

commit 4d48c89a785d28e8046042687bddc1b5789f6d5c
Author: rouslan <rouslan@chromium.org>
Date: Tue Jun 07 22:36:21 2016

Sanitize JSON string before parsing it.

This patch makes PaymentRequestImpl use JsonSanitizer.santize() to
validate and sanitize the JSON string before parsing it.

BUG=617634

Review-Url: https://codereview.chromium.org/2039303002
Cr-Commit-Position: refs/heads/master@{#398404}

[modify] https://crrev.com/4d48c89a785d28e8046042687bddc1b5789f6d5c/chrome/android/BUILD.gn
[modify] https://crrev.com/4d48c89a785d28e8046042687bddc1b5789f6d5c/chrome/android/java/DEPS
[modify] https://crrev.com/4d48c89a785d28e8046042687bddc1b5789f6d5c/chrome/android/java/src/org/chromium/chrome/browser/payments/PaymentRequestImpl.java
[modify] https://crrev.com/4d48c89a785d28e8046042687bddc1b5789f6d5c/components/safe_json/android/java/src/org/chromium/components/safejson/JsonSanitizer.java

Still to-do: Make JsonSanitizer return a sanitized JSONObject.

sebsg@ to the rescue: Make JsonSanitizer return a sanitized JSONObject similar to the C++ API in //components/safe_json.

Minor comment: I'd like the public java API to be named SafeJsonParser, just like the C++ side, and the JsonSanitizer should be an implementation detail of both that interface and the C++ one.

Minor comment on the minor comment: :-D In C++, the JsonSanitizer is exposed on purpose, because for Supervised User whitelists we run sanitization before writing them to disk, so we can later load them without the additional overhead. Only exposing SafeJsonParser would mean one unnecessary parsing/serialization roundtrip on Android.

Ah, I forgot we exposed JsonSanitizer directly to C++ too. Then we should have the Java API mirror the C++ one with both JsonSanitizer and SafejsonParser.

That sounds good :)