Credential disclosure via /proc/kcore path traversal
Published Jan 24, 2020 · Updated Aug 6, 2024
Path traversal in Vivotek PT7135 firmware 0300a and 0400a allows remote attackers to read camera memory and extract user credentials. The HTTP service accepts ../ segments in a crafted GET path and returns /proc/kcore, exposing a memory image that contains valid credentials. Firmware 0300a requires no authentication, while firmware 0400a requires an authenticated session; the demonstrated impact is credential disclosure.
Summary
What happened
Path traversal in Vivotek PT7135 firmware 0300a and 0400a allows remote attackers to read camera memory and extract user credentials. The HTTP service accepts ../ segments in a crafted GET path and returns /proc/kcore, exposing a memory image that contains valid credentials. Firmware 0300a requires no authentication, while firmware 0400a requires an authenticated session; the demonstrated impact is credential disclosure.
The record
- CVE
- CVE-2013-1597
- Published
- Jan 24, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 24, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Weakness, pattern, technique
Public exploit references
- Vivotek PT7135 path-traversal proof of conceptproof of concept · demonstrated
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