Response header injection via unvalidated classifier parameter
Published Feb 23, 2022 · Updated Aug 4, 2024
HTTP response header injection in Stanford CoreNLP 4.3.2 and earlier allows remote attackers to manipulate servlet response headers. NERServlet copies the unvalidated classifier request parameter into the classifier response header; outputFormat was handled similarly. An exposed NER web application is required, and crafted header content enables cache poisoning, cross-site scripting, redirects, or cookie manipulation.
Summary
What happened
HTTP response header injection in Stanford CoreNLP 4.3.2 and earlier allows remote attackers to manipulate servlet response headers. NERServlet copies the unvalidated classifier request parameter into the classifier response header; outputFormat was handled similarly. An exposed NER web application is required, and crafted header content enables cache poisoning, cross-site scripting, redirects, or cookie manipulation.
The record
- CVE
- CVE-2021-44550
- Published
- Feb 23, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-74, CWE-863, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 23, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo