-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update dependency json to v10 [security] #2464
Open
renovate
wants to merge
1
commit into
develop
Choose a base branch
from
renovate/npm-json-vulnerability
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/npm-json-vulnerability
branch
13 times, most recently
from
June 17, 2021 04:14
f42b81d
to
567bf30
Compare
renovate
bot
force-pushed
the
renovate/npm-json-vulnerability
branch
6 times, most recently
from
June 24, 2021 19:58
df371eb
to
5351e84
Compare
renovate
bot
force-pushed
the
renovate/npm-json-vulnerability
branch
7 times, most recently
from
July 1, 2021 04:26
3eabe6e
to
51c6e2c
Compare
renovate
bot
force-pushed
the
renovate/npm-json-vulnerability
branch
4 times, most recently
from
July 8, 2021 06:57
9ffc57f
to
d953119
Compare
renovate
bot
force-pushed
the
renovate/npm-json-vulnerability
branch
6 times, most recently
from
October 11, 2021 17:36
a3e152f
to
737587d
Compare
renovate
bot
force-pushed
the
renovate/npm-json-vulnerability
branch
3 times, most recently
from
October 19, 2021 01:26
816cd3c
to
2ef1f65
Compare
renovate
bot
force-pushed
the
renovate/npm-json-vulnerability
branch
8 times, most recently
from
October 27, 2021 05:30
d5b0f6c
to
91e8c16
Compare
renovate
bot
force-pushed
the
renovate/npm-json-vulnerability
branch
from
October 28, 2021 08:56
91e8c16
to
63f1005
Compare
renovate
bot
changed the title
chore(deps): update dependency json to 10.0.0 [security]
chore(deps): update dependency json to 10.0.0 [security] - abandoned
Feb 24, 2024
Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error. |
renovate
bot
changed the title
chore(deps): update dependency json to 10.0.0 [security] - abandoned
chore(deps): update dependency json to v10 [security]
Feb 26, 2024
renovate
bot
force-pushed
the
renovate/npm-json-vulnerability
branch
from
February 26, 2024 16:01
63f1005
to
dc12127
Compare
renovate
bot
changed the title
chore(deps): update dependency json to v10 [security]
chore(deps): update dependency json to v10 [security] - autoclosed
Mar 20, 2024
renovate
bot
changed the title
chore(deps): update dependency json to v10 [security] - autoclosed
chore(deps): update dependency json to v10 [security]
Mar 20, 2024
renovate
bot
force-pushed
the
renovate/npm-json-vulnerability
branch
from
March 20, 2024 19:24
dc12127
to
eee5fa3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
9.0.6
->10.0.0
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.
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-providedstrings as a "lookup", then you should upgrade.
For the
json
CLI, a "lookup" string is the 'foo' in:which allows you to lookup fields on the given JSON, e.g.:
If one of the lookup fields isn't a valid JS identifier, then the JS array
notation is supported:
Before this change,
json
would effectively exec the string between thebrackets as JS code such that things like the following were possible:
This change limits supported bracket syntax in lookups to a simple quoted
string:
Otherwise generating an error of the form:
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: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.