GHSA-c6m7-q6pr-c64r json
Vite Plugin React has a Source Code Exposure Vulnerability in React Server Components
published 11mo ago modified 10mo ago
- cvss
- 5.3
- 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
### Impact
`@vitejs/plugin-rsc` vendors `react-server-dom-webpack`, which contained a vulnerability in versions prior to 19.2.3. See details in React repository's advisory https://github.com/facebook/react/security/advisories/GHSA-925w-6v3x-g4j4
### Patches
Upgrade immediately to `@vitejs/plugin-rsc@0.5.7` or later.
Patch / fix
- npm @vitejs/plugin-rsc 0.5.7
Is GHSA-c6m7-q6pr-c64r 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 FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @vitejs/plugin-rsc | <0.5.7 |
0.5.7 |
Classification
References
Sources
- GitHub Advisory GHSA-c6m7-q6pr-c64r
- Maintainer advisory GHSA-c6m7-q6pr-c64r
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.