Skip to content

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 27, 2025

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.


This PR contains the following updates:

Package Type Update Change Age Confidence
json devDependencies pin ^9.0.4 -> 9.0.6 age confidence
json devDependencies major 9.0.6 -> 10.0.0 age confidence

GitHub Vulnerability Alerts

CVE-2020-7712

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

Add the preset :preserveSemverRanges to your config if you don't want to pin your dependencies.


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: Branch creation - "" in timezone America/New_York, Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

@renovate renovate bot force-pushed the renovate/npm-json-vulnerability branch from e69d689 to 42ff5f0 Compare February 10, 2025 21:39
@renovate renovate bot added the security label Feb 10, 2025
@renovate renovate bot force-pushed the renovate/npm-json-vulnerability branch from 42ff5f0 to 48b6f50 Compare February 10, 2025 21:41
@renovate renovate bot force-pushed the renovate/npm-json-vulnerability branch from 48b6f50 to fac07fe Compare February 22, 2025 02:24
@renovate renovate bot requested a review from a team as a code owner February 22, 2025 02:24
@renovate renovate bot force-pushed the renovate/npm-json-vulnerability branch from fac07fe to 629774a Compare August 10, 2025 13:08
@renovate renovate bot changed the title chore(deps): update dependency json to v10 [security] chore(deps): pin dependency json [security] Aug 10, 2025
@renovate renovate bot force-pushed the renovate/npm-json-vulnerability branch from 629774a to dcba07c Compare August 13, 2025 12:08
@renovate renovate bot force-pushed the renovate/npm-json-vulnerability branch 2 times, most recently from 0512b49 to b7385e2 Compare August 24, 2025 00:28
@renovate renovate bot force-pushed the renovate/npm-json-vulnerability branch from b7385e2 to 0839855 Compare August 31, 2025 13:04
@renovate renovate bot force-pushed the renovate/npm-json-vulnerability branch 2 times, most recently from 093aae0 to a19bb82 Compare September 25, 2025 18:16
Copy link

github-actions bot commented Sep 25, 2025

Test report for scratch-svg-renderer

  1 files  ±0   60 suites  ±0   0s ⏱️ ±0s
124 tests ±0  124 ✅ ±0  0 💤 ±0  0 ❌ ±0 
276 runs  ±0  275 ✅ ±0  1 💤 ±0  0 ❌ ±0 

Results for commit 791ce75. ± Comparison against base commit cdaabec.

♻️ This comment has been updated with latest results.

Copy link

github-actions bot commented Sep 25, 2025

Test report for scratch-render

  1 files  ±0   55 suites  ±0   2s ⏱️ -1s
209 tests ±0  209 ✅ ±0  0 💤 ±0  0 ❌ ±0 
279 runs  ±0  279 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 791ce75. ± Comparison against base commit cdaabec.

♻️ This comment has been updated with latest results.

Copy link

github-actions bot commented Sep 25, 2025

Test report for scratch-vm

    1 files  ±0    770 suites  ±0   1m 5s ⏱️ ±0s
1 686 tests ±0  1 686 ✅ ±0   0 💤 ±0  0 ❌ ±0 
4 891 runs  ±0  4 861 ✅ ±0  30 💤 ±0  0 ❌ ±0 

Results for commit 791ce75. ± Comparison against base commit cdaabec.

♻️ This comment has been updated with latest results.

Copy link

github-actions bot commented Sep 25, 2025

Test report for scratch-gui

  2 files  ±0   61 suites  ±0   9m 6s ⏱️ -34s
389 tests ±0  380 ✅ ±0  9 💤 ±0  0 ❌ ±0 
407 runs  ±0  398 ✅ ±0  9 💤 ±0  0 ❌ ±0 

Results for commit 791ce75. ± Comparison against base commit cdaabec.

♻️ This comment has been updated with latest results.

@renovate renovate bot force-pushed the renovate/npm-json-vulnerability branch 12 times, most recently from 0f74666 to a56e051 Compare September 29, 2025 16:28
@renovate renovate bot force-pushed the renovate/npm-json-vulnerability branch 13 times, most recently from c7b4da2 to 8e8b133 Compare October 4, 2025 13:05
@renovate renovate bot force-pushed the renovate/npm-json-vulnerability branch from 8e8b133 to 791ce75 Compare October 6, 2025 04:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants