Session hijacking via hard-coded session token
Published Jun 18, 2021 · Updated Sep 16, 2024
Improper access control in Bosch B426-family firmware allows remote attackers to hijack an active web configuration session. The lgs.cgi module accepts a hard-coded session token instead of validating a session-specific credential. Network access and an active user session are required; exploitation exposes configuration pages without login credentials.
Summary
What happened
Improper access control in Bosch B426-family firmware allows remote attackers to hijack an active web configuration session. The lgs.cgi module accepts a hard-coded session token instead of validating a session-specific credential. Network access and an active user session are required; exploitation exposes configuration pages without login credentials.
The record
- CVE
- CVE-2021-23845
- Published
- Jun 18, 2021
- Updated
- Sep 16, 2024
- Vendor
- Bosch Security Systems B.V.
- Product
- B426-M Firmware
- Classifications
- CWE-284, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 18, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <03.10
What conditions does exploitation require?
What is affected?
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.
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