CVE-2019-6802 json
CRLF Injection in pypiserver
published 7y ago modified 4mo ago also GHSA-mh24-7wvg-v88g , PYSEC-2019-113 , EUVD-2019-0108
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.8%
- EPSS 3.8% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
CRLF Injection in pypiserver 1.2.5 and below allows attackers to set arbitrary HTTP headers and possibly conduct XSS attacks via a %0d%0a in a URI.
Patch / fix
Is CVE-2019-6802 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 FencerExploit prediction
3.80% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template Pypiserver <1.2.5 - Carriage Return Line Feed Injection nuclei detection template
- github.com https://github.com/pypiserver/pypiserver/issues/237 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
| GitHub | 3.0 | 6.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | pypiserver | <1.2.6 |
1.2.6 |
Classification
References
-
github.com
/pypiserver/pypiserver/commit/1375a67c55a9b8d4619df30d2a1c0b239d7357e6
web
-
github.com
/pypiserver/pypiserver/issues/237
web, exploit, third-party-advisory, report
-
nvd.nist.gov
/vuln/detail/CVE-2019-6802
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/pypiserver/PYSEC-2019-113.yaml
web
-
github.com
/pypiserver/pypiserver
package
-
github.com
/advisories/GHSA-mh24-7wvg-v88g
advisory
Sources
- CVE List CVE-2019-6802
- GitHub Advisory GHSA-mh24-7wvg-v88g
- NVD CVE-2019-6802
- OSV PYSEC-2019-113
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.