Session Smart Router and Session Smart Conductor: Lack of integrity verification in cache files causes arbitrary code execution and privilege escalation
- 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 Session Smart Router and Session Smart Conductor products from Juniper Networks are affected, specifically their PCLI component. An attacker who can write to the model cache directory could exploit unverified cache files to run arbitrary code and gain higher privileges on the system.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
An Insufficient Verification of Data Authenticity vulnerability in PCLI in Juniper Networks Session Smart Router and Session Smart Conductor allows an attacker with write access to the model cache directory to execute arbitrary code and escalate privileges via the processing of unverified cache files.
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