Skip to content
Fencer Intel
high 8.8

GHSA-rw75-cc5p-q7c9 json

Import-time code execution in @orval/fetch via unescaped OpenAPI response status key emitted into a generated TypeScript type

published last mo. modified last mo.

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository orval-labs/orval. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.

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

Summary

Security advisory published by the maintainers of orval-labs/orval for @orval/fetch: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.

Patch / fix

  • npm @orval/fetch >=8.33.0

Is GHSA-rw75-cc5p-q7c9 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
the maintainers 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm @orval/fetch
>=8.30.0, <=8.32.0
>=8.33.0

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code
  • CWE-95 Improper Neutralization of Directives in Dynamically Evaluated Code
  • CWE-116 Improper Encoding or Escaping of Output

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 orval-labs/orval published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.