Skip to content
Fencer Intel
critical 10.0

GHSA-fmh4-wr37-44fp json

React Server Components are Vulnerable to RCE

published 11mo ago modified 11mo ago

cvss
10.0
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Summary

`@vitejs/plugin-rsc` vendors `react-server-dom-webpack`, which contained an unauthenticated remote code execution vulnerability in versions prior to 19.0.1, 19.1.2, and 19.2.1. See details in React repository's advisory https://github.com/facebook/react/security/advisories/GHSA-fv66-9v8q-g76r

### Impact

Applications using affected versions of `@vitejs/plugin-rsc` are vulnerable to unauthenticated remote code execution through deserialization of untrusted data. An attacker can execute arbitrary code remotely without authentication, affecting confidentiality, integrity, and availability.

### Recommendations

Upgrade immediately to `@vitejs/plugin-rsc@0.5.3` or later.

### Workarounds

Applications not using server-side React or React Server Components are unaffected.

Patch / fix

  • npm @vitejs/plugin-rsc 0.5.3

Is GHSA-fmh4-wr37-44fp in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm @vitejs/plugin-rsc
<0.5.3
0.5.3

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of vitejs/vite-plugin-react published their own advisory on GitHub. Reviewed sources take precedence over it.