CVE-2024-5096
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability classified as problematic was found in Hipcam Device up to 20240511. This vulnerability affects unknown code of the file /log/wifi.mac of the component MAC Address Handler. The manipulation leads to information disclosure. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. VDB-265078 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn information disclosure vulnerability exists in Hipcam devices up to the May 2024 firmware version. The /log/wifi.mac endpoint, part of the MAC Address Handler component, is accessible without authentication and exposes MAC addresses to remote attackers. The exploit has been publicly disclosed, making this a readily exploitable issue.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Hipcam device on the networkLocate Hipcam-specific devices by reviewing network device inventories, checking MAC vendor prefixes (Hipcam OUI), or accessing the device's web interface at its IP address and noting the Hipcam branding/logoAffected if The device is a Hipcam branded camera or NVR system
-
Determine firmware versionAccess the device's administration interface or check the system info page, typically found at /system or /device-info endpoints, or via the device's mobile app. Compare the firmware date to May 2024 or earlierAffected if Firmware version is dated May 2024 or earlier (any version in the affected range)
-
Test unauthenticated access to /log/wifi.mac endpointUsing a web browser or curl command, navigate to http://[device-ip]/log/wifi.mac without providing any login credentialsAffected if The endpoint returns a response without requiring authentication
-
Verify MAC address exposureExamine the response from the /log/wifi.mac endpoint for MAC addresses (format XX:XX:XX:XX:XX:XX or similar) in the returned dataAffected if The endpoint returns one or more MAC addresses without requiring authentication
A Hipcam device running firmware from May 2024 or earlier with the /log/wifi.mac endpoint accessible without authentication and returning MAC addresses indicates the environment is affected by CVE-2024-5096.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince the vendor did not respond to early disclosure and no patch is expected, implement compensating controls such as network segmentation to restrict access to the affected device, add firewall rules to limit who can reach the /log/wifi.mac endpoint, or replace the device with a supported alternative.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5096 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5096 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data