CVE-2013-7299: framework/common/messageheaderparser.cpp in Tntnet before 2.2.1 allows remote attackers to obtain sensitive in
CVE-2013-7299 is a medium-severity flaw (CVSS 5.0) affecting tntnet. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
framework/common/messageheaderparser.cpp in Tntnet before 2.2.1 allows remote attackers to obtain sensitive information via a header that ends in \n instead of \r\n, which prevents a null terminator from being added and causes Tntnet to include headers from other requests.
Why this priority
- No elevated risk signals yet
A fixed release or distro patch exists.
Risk facts
| CVSS score | 5.0 (Medium) |
| EPSS exploit chance | 2.5% (top 15%) |
| CISA exploited list | No |
| Weakness | CWE-200 |
| Published | 2014-01-26 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2013-7299?
tntnet: upgrade to newer than 2.2. Exact commands for each OS are on this page.
Is CVE-2013-7299 being exploited?
CVE-2013-7299 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2013-7299 affect?
CVE-2013-7299 affects tntnet. Severity is medium (CVSS 5.0). framework/common/messageheaderparser.cpp in Tntnet before 2.2.1 allows remote attackers to obtain sensitive information via a header that ends in \n instead of \r\n, which prevents a null terminator from being added and causes Tntnet to inc
How urgent is CVE-2013-7299?
Priority 39/100. No elevated risk signals yet.