chore(deps): update dependency json to v10 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
json	9.0.6 → 10.0.0

---

trentm/json vulnerable to command injection

CVE-2020-7712 / GHSA-3c6g-pvg8-gqw2

More information

Details

This affects the package json before 10.0.0. It is possible to inject arbritary commands using the parseLookup function.

Severity

• CVSS Score: 7.2 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

References

• https://nvd.nist.gov/vuln/detail/CVE-2020-7712
• https://github.com/trentm/json/issues/144
• https://github.com/trentm/json/pull/145
• https://github.com/trentm/json/commit/cc4798169f9e0f181f8aa61905b88479badcd483
• https://lists.apache.org/thread.html/r37c0e1807da7ff2bdd028bbe296465a6bbb99e2320dbe661d5d8b33b@%3Cissues.zookeeper.apache.org%3E
• https://lists.apache.org/thread.html/r3b04f4e99a19613f88ae088aa18cd271231a3c79dfff8f5efa8cda61@​%3Cissues.zookeeper.apache.org%3E
• https://lists.apache.org/thread.html/r5f17bfca1d6e7f4b33ae978725b2fd62a9f1b3111696eafa9add802d@%3Cissues.zookeeper.apache.org%3E
• https://lists.apache.org/thread.html/r8d2e174230f6d26e16c007546e804c343f1f68956f526daaafa4aaae@%3Cdev.zookeeper.apache.org%3E
• https://lists.apache.org/thread.html/r977a907ecbedf87ae5ba47d4c77639efb120f74d4d1b3de14a4ef4da@%3Cissues.flink.apache.org%3E
• https://lists.apache.org/thread.html/r9c6d28e5b9a9b3481b7d1f90f1c2f75cd1a5ade91038426e0fb095da@%3Cdev.flink.apache.org%3E
• https://lists.apache.org/thread.html/ra890c24b3d90be36daf48ae76b263acb297003db24c1122f8e4aaef2@​%3Cissues.flink.apache.org%3E
• https://lists.apache.org/thread.html/rb023d54a46da1ac0d8969097f5fecc79636b07d3b80db7b818a5c55c@%3Cissues.zookeeper.apache.org%3E
• https://lists.apache.org/thread.html/rb2b981912446a74e14fe6076c4b7c7d8502727ea0718e6a65a9b1be5@​%3Cissues.zookeeper.apache.org%3E
• https://lists.apache.org/thread.html/rb89bd82dffec49f83b49e9ad625b1b63a408b3c7d1a60d6f049142a0@​%3Cissues.flink.apache.org%3E
• https://lists.apache.org/thread.html/rba7ea4d75d6a8e5b935991d960d9b893fd30e576c4d3b531084ebd7d@%3Cissues.flink.apache.org%3E
• https://lists.apache.org/thread.html/rd9b9cc843f5cf5b532bdad9e87a817967efcf52b917e8c43b6df4cc7@​%3Cissues.zookeeper.apache.org%3E
• https://lists.apache.org/thread.html/rec8bb4d637b04575da41cfae49118e108e95d43bfac39b7b698ee4db@%3Cissues.zookeeper.apache.org%3E
• https://lists.apache.org/thread.html/ree3abcd33c06ee95ab59faa1751198a1186d8941ddc2c2562c12966c@%3Cissues.zookeeper.apache.org%3E
• https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-608931
• https://snyk.io/vuln/SNYK-JS-JSON-597481
• https://www.oracle.com//security-alerts/cpujul2021.html
• https://www.oracle.com/security-alerts/cpujan2022.html
• https://www.oracle.com/security-alerts/cpujul2022.html
• https://github.com/advisories/GHSA-3c6g-pvg8-gqw2

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

trentm/json (json)

v10.0.0

Compare Source

• Backward incompatible and security-related change to parsing "lookup" strings.

  This version restricts the supported syntax for bracketed "lookup"
  strings to fix a possible
  vulnerability (CVE-2020-7712). With a carefully crafted lookup string,
  command injection was possible. See
  #​144 for a repro. If you use
  json (the CLI or as a node.js module) and run arbitrary user-provided
  strings as a "lookup", then you should upgrade.

  For the json CLI, a "lookup" string is the 'foo' in:

    echo ...some json... | json foo
  

  which allows you to lookup fields on the given JSON, e.g.:

    $ echo '{"foo": {"bar": "baz"}}' | json foo.bar
    baz
  

  If one of the lookup fields isn't a valid JS identifier, then the JS array
  notation is supported:

    $ echo '{"https://example.com": "my-value"}' | json '["https://example.com"]'
    my-value
  

  Before this change, json would effectively exec the string between the
  brackets as JS code such that things like the following were possible:

    $ echo '{"foo3": "bar"}' | json '["foo" + 3]'
    bar
  

  This change limits supported bracket syntax in lookups to a simple quoted
  string:

    ["..."]
    ['...']
    [`...`]      # no variable interpolation
  

  Otherwise generating an error of the form:

    json: error: invalid bracketed lookup string: "[\"foo\" + 3]" (must be of the form ['...'], ["..."], or [`...`])
  

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Test Results

    8 files  ±0  1 117 suites  ±0   15m 22s ⏱️ +36s
2 885 tests ±0  2 877 ✅ ±0   8 💤 ±0  0 ❌ ±0 
6 511 runs  ±0  6 472 ✅ ±0  39 💤 ±0  0 ❌ ±0 

Results for commit d223a46. ± Comparison against base commit faf7f68.

♻️ This comment has been updated with latest results.