VStarcam O-KAM SuperIPCam P2P Session Teardown SuperIPCam.exe FUN_005a2d44 use after free
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts record no workaround. Nothing in them documents a mitigation to apply until a fix is released.
- 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
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 19/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- 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 VStarcam O-KAM SuperIPCam Windows application, which handles peer-to-peer connection sessions for VStarcam IP cameras, contains a memory flaw that can be triggered remotely. Successful exploitation could cause the program to crash or allow an attacker to run malicious code, and a public exploit for it has been disclosed.
Read the original description
A vulnerability was determined in VStarcam O-KAM SuperIPCam 1.3.3.32. Affected by this issue is the function FUN_005a2d44 of the file SuperIPCam.exe of the component P2P Session Teardown. This manipulation causes use after free. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.
What to do
Workaround: The checked facts record no workaround. Nothing in them documents a mitigation to apply until a fix is released.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- VStarcam O-KAM SuperIPCam
1.3.3.32
Evidence 5
- Advisory
- Advisory
- Advisory
- Advisory
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120337
What does this mean?
A session object is torn down while a concurrent sample callback in SuperIPCam.exe still races for the same object. The race corrupts the process heap and causes a null-pointer dereference that crashes the program.Source: gist.github.com
Am I affected, and how do I check?
The checked facts do not list affected version ranges for VStarcam O-KAM SuperIPCam. The bug needs a sample callback to run during session teardown, which takes a targeted flood of messages to trigger. Compare your SuperIPCam.exe version with the vendor's advisory to see if it is listed.Source: gist.github.com
What should I do about it?
The checked facts name no fixed version, so no upgrade target is confirmed. Check the vendor's channels for an update to SuperIPCam.Source: gist.github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The checked facts record no workaround. Nothing in them documents a mitigation to apply until a fix is released.Source: gist.github.com