Some access control products are vulnerable to a session hijacking attack because the product does not update the session ID after a user su
- 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 V1.4.0_build221212, V3.2.30_build221223, V3.14.0_build230117, V3.3.8_build230112, V3.5.0_build220706
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Some access control products are vulnerable to a session hijacking attack because the product does not update the session ID after a user successfully logs in. To exploit the vulnerability, attackers have to request the session ID at the same time as a valid user logs in, and gain device operation permissions by forging the IP and session ID of an authenticated user.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- hikvision DS-K1T804AXX
From V1.4.0_build221212 · fixed in V1.4.0_build221212
- hikvision DS-K1T341AXX
From V3.2.30_build221223 · fixed in V3.2.30_build221223
- hikvision DS-K1T671XXX
From V3.2.30_build221223 · fixed in V3.2.30_build221223
- hikvision DS-K1T343XXX
From V3.14.0_build230117 · fixed in V3.14.0_build230117
- hikvision DS-K1T341C
From V3.3.8_build230112 · fixed in V3.3.8_build230112
- hikvision DS-K1T320XXX
From V3.5.0_build220706 · fixed in V3.5.0_build220706