CVE-2011-10042http-session CRLF injection
CVE-2011-10042 is a CRLF injection in http-session, not yet scored.
Why this priority: Not scored yet, and no exploitation signal.
Published · Updated · NVD status: Received
What it is
Line breaks in input end up in headers or logs, letting an attacker add lines of their own.
How it is reached
The record does not say yet how the flaw is reached; the description below is the best guide until it is scored.
What an attacker gains
Its impact has not been scored yet. In practice, this kind of flaw lets an attacker smuggle requests past the proxy's checks.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade http-session to 0.43 or later.
Description from NVD
HTTP::Session versions before 0.43 for Perl allow memcached command injection via unfiltered session ids in HTTP::Session::Store::Memcached.
The session id from the client's cookie reaches memcached unchanged as the cache key.
A CR and LF in the session id end the cache command early, and the server reads the bytes after them as further commands.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Proxies, load balancers and the servers behind them. The flaw sits between a front-end proxy and its back end.
Trust boundaries in play
- Between a front-end proxy and its back end. An attacker who crosses it can smuggle requests past the proxy's checks.
Questions to answer about your own systems
- Where does http-session run in your systems, and at which version?
- Which of those instances are reachable by people you do not trust?
- What can it reach once compromised: which data stores, secrets and services?
Read more
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.