🚨 [security] Update all of babel7 7.4.3 → 7.29.7 (minor)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​babel/core (7.4.3 → 7.29.7) · Repo · Changelog

Security Advisories 🚨

🚨 @babel/core: Arbitrary File Read via sourceMappingURL Comment

Impact

Using @babel/core to compile maliciously crafted code can allow ab attacker to read any source map from the system that is running Babel, if these conditions are all true:

• the attacker controls the input source code
• the attacker can read the output source code
• the attacker knows the path of the source map file that they want to read

Users that only compile trusted code are not impacted.

Patches

The vulnerability has been fixed in @babel/core@7.29.6 and @babel/core@8.0.0-rc.6.

Workarounds

Callers can mitigate the issue without upgrading by setting inputSourceMap: false in their Babel options.

Callers can also manually extract the #sourceMappingURL comment from the input source code, validate whether the source map that it links to is allowed to be read, and if it is pass an object to inputSourceMap (passing false when it's not).

Credits

Thanks Teodor-Cristian Radoi for reporting the vulnerability.

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by 2 commits:

• v7.29.7
• Add v7.29.6 to CHANGELOG.md [skip ci]

✳️ @​babel/runtime (7.4.3 → 7.29.7) · Repo · Changelog

Security Advisories 🚨

🚨 Babel has inefficient RegExp complexity in generated code with .replace when transpiling named capturing groups

Impact

When using Babel to compile regular expression named capturing groups, Babel will generate a polyfill for the .replace method that has quadratic complexity on some specific replacement pattern strings (i.e. the second argument passed to .replace).

Your generated code is vulnerable if all the following conditions are true:

• You use Babel to compile regular expression named capturing groups
• You use the .replace method on a regular expression that contains named capturing groups
• Your code uses untrusted strings as the second argument of .replace

If you are using @babel/preset-env with the targets option, the transform that injects the vulnerable code is automatically enabled if:

• you use duplicated named capturing groups, and target any browser older than Chrome/Edge 126, Opera 112, Firefox 129, Safari 17.4, or Node.js 23
• you use any named capturing groups, and target any browser older than Chrome 64, Opera 71, Edge 79, Firefox 78, Safari 11.1, or Node.js 10

You can verify what transforms @babel/preset-env is using by enabling the debug option.

Patches

This problem has been fixed in @babel/helpers and @babel/runtime 7.26.10 and 8.0.0-alpha.17, please upgrade. It's likely that you do not directly depend on @babel/helpers, and instead you depend on @babel/core (which itself depends on @babel/helpers). Upgrading to @babel/core 7.26.10 is not required, but it guarantees that you are on a new enough @babel/helpers version.

Please note that just updating your Babel dependencies is not enough: you will also need to re-compile your code.

Workarounds

If you are passing user-provided strings as the second argument of .replace on regular expressions that contain named capturing groups, validate the input and make sure it does not contain the substring $< if it's then not followed by > (possibly with other characters in between).

References

This vulnerability was reported and fixed in #17173.

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by 2 commits:

• v7.29.7
• Add v7.29.6 to CHANGELOG.md [skip ci]

↗️ @​babel/helpers (indirect, 7.4.3 → 7.29.7) · Repo · Changelog

Security Advisories 🚨

🚨 Babel has inefficient RegExp complexity in generated code with .replace when transpiling named capturing groups

Impact

When using Babel to compile regular expression named capturing groups, Babel will generate a polyfill for the .replace method that has quadratic complexity on some specific replacement pattern strings (i.e. the second argument passed to .replace).

Your generated code is vulnerable if all the following conditions are true:

• You use Babel to compile regular expression named capturing groups
• You use the .replace method on a regular expression that contains named capturing groups
• Your code uses untrusted strings as the second argument of .replace

If you are using @babel/preset-env with the targets option, the transform that injects the vulnerable code is automatically enabled if:

• you use duplicated named capturing groups, and target any browser older than Chrome/Edge 126, Opera 112, Firefox 129, Safari 17.4, or Node.js 23
• you use any named capturing groups, and target any browser older than Chrome 64, Opera 71, Edge 79, Firefox 78, Safari 11.1, or Node.js 10

You can verify what transforms @babel/preset-env is using by enabling the debug option.

Patches

This problem has been fixed in @babel/helpers and @babel/runtime 7.26.10 and 8.0.0-alpha.17, please upgrade. It's likely that you do not directly depend on @babel/helpers, and instead you depend on @babel/core (which itself depends on @babel/helpers). Upgrading to @babel/core 7.26.10 is not required, but it guarantees that you are on a new enough @babel/helpers version.

Please note that just updating your Babel dependencies is not enough: you will also need to re-compile your code.

Workarounds

If you are passing user-provided strings as the second argument of .replace on regular expressions that contain named capturing groups, validate the input and make sure it does not contain the substring $< if it's then not followed by > (possibly with other characters in between).

References

This vulnerability was reported and fixed in #17173.

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by 2 commits:

• v7.29.7
• Add v7.29.6 to CHANGELOG.md [skip ci]

↗️ json5 (indirect, 2.1.0 → 2.2.3) · Repo · Changelog

Security Advisories 🚨

🚨 Prototype Pollution in JSON5 via Parse Method

The parse method of the JSON5 library before and including version 2.2.1 does not restrict parsing of keys named __proto__, allowing specially crafted strings to pollute the prototype of the resulting object.

This vulnerability pollutes the prototype of the object returned by JSON5.parse and not the global Object prototype, which is the commonly understood definition of Prototype Pollution. However, polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations.

Impact

This vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from JSON5.parse. The actual impact will depend on how applications utilize the returned object and how they filter unwanted keys, but could include denial of service, cross-site scripting, elevation of privilege, and in extreme cases, remote code execution.

Mitigation

This vulnerability is patched in json5 v2.2.2 and later. A patch has also been backported for json5 v1 in versions v1.0.2 and later.

Details

Suppose a developer wants to allow users and admins to perform some risky operation, but they want to restrict what non-admins can do. To accomplish this, they accept a JSON blob from the user, parse it using JSON5.parse, confirm that the provided data does not set some sensitive keys, and then performs the risky operation using the validated data:

const JSON5 = require('json5');
const doSomethingDangerous = (props) => {

if (props.isAdmin) {

console.log('Doing dangerous thing as admin.');

} else {

console.log('Doing dangerous thing as user.');

}

};
const secCheckKeysSet = (obj, searchKeys) => {

let searchKeyFound = false;

Object.keys(obj).forEach((key) => {

if (searchKeys.indexOf(key) > -1) {

searchKeyFound = true;

}

});

return searchKeyFound;

};
const props = JSON5.parse('{"foo": "bar"}');

if (!secCheckKeysSet(props, ['isAdmin', 'isMod'])) {

doSomethingDangerous(props); // "Doing dangerous thing as user."

} else {

throw new Error('Forbidden...');

}

If the user attempts to set the isAdmin key, their request will be rejected:

const props = JSON5.parse('{"foo": "bar", "isAdmin": true}');
if (!secCheckKeysSet(props, ['isAdmin', 'isMod'])) {
  doSomethingDangerous(props);
} else {
  throw new Error('Forbidden...'); // Error: Forbidden...
}

However, users can instead set the __proto__ key to {"isAdmin": true}. JSON5 will parse this key and will set the isAdmin key on the prototype of the returned object, allowing the user to bypass the security check and run their request as an admin:

const props = JSON5.parse('{"foo": "bar", "__proto__": {"isAdmin": true}}');
if (!secCheckKeysSet(props, ['isAdmin', 'isMod'])) {
  doSomethingDangerous(props); // "Doing dangerous thing as admin."
} else {
  throw new Error('Forbidden...');
}

Release Notes

2.2.3

• Fix: json5@2.2.3 is now the 'latest' release according to npm instead of v1.0.2. ([#299])

2.2.2

• Fix: Properties with the name __proto__ are added to objects and arrays.
  (#199) This also fixes a prototype pollution vulnerability reported by
  Jonathan Gregson! (#295).

2.2.1

• Fix: Removed dependence on minimist to patch CVE-2021-44906. ([#266])

2.2.0

• New: Accurate and documented TypeScript declarations are now included. There is no need to install @types/json5. ([#236], [#244])

2.1.3

v2.1.3 [code, diff]

• Fix: An out of memory bug when parsing numbers has been fixed. ([#228], [#229])

2.1.2

• Fix: Bump minimist to v1.2.5. ([#222])

2.1.1

• New: package.json and package.json5 include a module property so
  bundlers like webpack, rollup and parcel can take advantage of the ES Module
  build. ([#208])
• Fix: stringify outputs \0 as \\x00 when followed by a digit. ([#210])
• Fix: Spelling mistakes have been fixed. ([#196])

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 62 commits:

• 2.2.3
• docs: update CHANGELOG for v2.2.3
• docs(security): use GitHub security advisories
• docs: publish a security policy
• docs(template): bug -> bug report
• 2.2.2
• docs: update CHANGELOG for v2.2.2
• fix: add __proto__ to objects and arrays
• Readme: slight tweak to intro
• Improve example in readme
• Improve readme (e.g. explain JSON5 better!) (#291)
• docs: fix spelling of Aseem
• test: require tap as t in cli tests
• test: remove mocha syntax from tests
• docs: update installation and usage for modules
• docs: update package descript to match branding
• docs: update browser usage
• docs: update Installation and Usage header
• docs: update headers for CJS and modules usage
• Add ESM usage to README
• docs: update incorrect link in CHANGELOG
• build: lint before testing
• build: use npm-run-all
• docs: rename master branch to main
• docs: update Travis CI badge and link
• ci: remove Node.js v6 from Travis due to npm bug
• chore: fix broken travis-ci status badge
• Revert "Replace Travis CI with GitHub Actions"
• Merge pull request #275 from rhysd/github-actions
• ci: remove .travis.yml
• ci: replace Travis CI badge with GitHub Actions badge
• ci: add GitHub Actions workflow
• 2.2.1
• docs: update CHANGELOG for v2.2.1
• fix: remove minimist
• 2.2.0
• docs: update CHANGELOG for v2.2.0
• docs: update Travis CI badge
• docs: add missing links to CHANGELOG
• feat: add TypeScript delcarations for module files
• feat: add types declaration file with entry in package.json
• 2.1.3
• Update CHANGELOG for v2.1.3
• Add missing CHANGELOG for v2.1.2
• Merge branch 'master' of github.com:json5/json5
• Fix OOM when parsing bare hex number.
• Add test cases for bare number literals, including hex.
• 2.1.2
• Merge branch 'master' of github.com:json5/json5
• minimist library updated to the latest version
• Merge branch 'master' of github.com:json5/json5
• README: fixed dead link to json_parse.js
• 2.1.1
• docs: update CHANGELOG
• build: update package.json5
• test: fix typo
• fix: stringify `\0` as `\\x00` in some cases
• Add module entry to package.json
• Correct spelling mistakes
• Update Travis CI Node.js versions
• Update dependencies
• Remove unnecessary ESLint config options

🆕 @​babel/compat-data (added, 7.29.7)

🆕 @​babel/helper-compilation-targets (added, 7.29.7)

🆕 @​babel/helper-globals (added, 7.29.7)

🆕 @​babel/helper-string-parser (added, 7.29.7)

🆕 @​babel/helper-validator-identifier (added, 7.29.7)

🆕 @​babel/helper-validator-option (added, 7.29.7)

🆕 @​jridgewell/gen-mapping (added, 0.3.13)

🆕 @​jridgewell/remapping (added, 2.3.5)

🆕 @​jridgewell/resolve-uri (added, 3.1.2)

🆕 @​jridgewell/sourcemap-codec (added, 1.5.5)

🆕 @​jridgewell/trace-mapping (added, 0.3.31)

🆕 baseline-browser-mapping (added, 2.10.37)

🆕 browserslist (added, 4.28.2)

🆕 caniuse-lite (added, 1.0.30001799)

🆕 electron-to-chromium (added, 1.5.372)

🆕 escalade (added, 3.2.0)

🆕 gensync (added, 1.0.0-beta.2)

🆕 node-releases (added, 2.0.47)

🆕 picocolors (added, 1.1.1)

🆕 update-browserslist-db (added, 1.2.3)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)