Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

GHSA-wjfc-pgfp-pv9c nyholm/psr7

MEDIUM

GHSA-wjfc-pgfp-pv9c is a medium-severity (CVSS 5.3) vulnerability in nyholm/psr7. A fix is available for nyholm/psr7 — see the affected versions and patch details below.

Improper Input Validation in nyholm/psr7

Published
Apr 21, 2023
Updated
Nov 29, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐘nyholm/psr7

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Improper header parsing. An attacker could sneak in a newline (\n) into both the header names and values. While the specification states that \r\n\r\n is used to terminate the header list, many servers in the wild will also accept \n\n.

Patches

The issue is patched in 1.6.1.

Workarounds

There are no known workarounds.

References

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistnyholm/psr7all versions1.6.1composer require nyholm/psr7:^1.6.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nyholm/psr7, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update nyholm/psr7 to 1.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wjfc-pgfp-pv9c is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-wjfc-pgfp-pv9c can be triaged on real exposure rather than presence alone.

Tailored to GHSA-wjfc-pgfp-pv9c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Improper header parsing. An attacker could sneak in a newline (`\n`) into both the header names and values. While the specification states that `\r\n\r\n` is used to terminate the header list, many servers in the wild will also accept `\n\n`. ### Patches The issue is patched in 1.6.1. ### Workarounds There are no known workarounds. ### References * https://www.rfc-editor.org/rfc/rfc7230#section-3.2.4
O3 Security · Impact-Aware SCA

Is GHSA-wjfc-pgfp-pv9c in your dependencies?

O3 Security finds GHSA-wjfc-pgfp-pv9c across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-wjfc-pgfp-pv9c: nyholm/psr7 | O3 Security