Session Smart Router and Session Smart Conductor: Unsanitized input causes HTTP response splitting
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.0.5, 7.1.7, 7.2.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The web server in Juniper Networks Session Smart Router and Session Smart Conductor products is affected. An attacker can exploit unsanitized request body parameters to inject arbitrary HTTP headers into responses, which could enable HTTP response splitting attacks against users or the device.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
An Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in the web server in Juniper Networks Session Smart Router and Session Smart Conductor allows an attacker to inject arbitrary HTTP headers via unsanitized request body parameters.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Juniper Networks Session Smart Router
fixed in 7.0.5; From 7.1.0 · fixed in 7.1.7; From 7.2.0 · fixed in 7.2.3
- Juniper Networks Session Smart Conductor
fixed in 7.0.5; From 7.1.0 · fixed in 7.1.7; From 7.2.0 · fixed in 7.2.3