Skip to content
Fencer Intel
critical 9.8

GHSA-mgc4-wqv7-4pxm json

SwiftNIO vulnerable to HTTP request smuggling using malformed Transfer-Encoding header

published 3y ago modified 3y ago

cvss
9.8
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

Affected SwiftNIO systems are vulnerable to request smuggling attacks, in which they parse a given HTTP message differently from other network parties, potentially seeing a different number of requests than other servers. This can lead to failures of authentication, routing, and other issues.

This vulnerability can be found in the bundled copy of the Node.JS HTTP parser used in the `NIOHTTP1` module.

### Workarounds

No workaround is available, users must upgrade.

### References

https://nodejs.org/en/blog/vulnerability/february-2020-security-releases/#http-request-smuggling-using-malformed-transfer-encoding-header-critical-cve-2019-15605

Patch / fix

  • swift github.com/apple/swift-nio 1.14.2, 2.13.1

Is GHSA-mgc4-wqv7-4pxm 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 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
swift github.com/apple/swift-nio
>=1.0.0, <1.14.2
>=2.0.0, <2.13.1
1.14.2
2.13.1

Classification

Weakness
  • CWE-444 Inconsistent Interpretation of HTTP Requests

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.