dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2024-48792

HIGH · 7.5 CVSS v3.1 Published 2024-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An issue in Hideez com.hideez 2.7.8.3 allows a remote attacker to obtain sensitive information via the firmware update process.

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 · moderate confidence

Vulnerability in Hideez app (com.hideez) version 2.7.8.3 allows a remote attacker to obtain sensitive information through the firmware update process. The issue appears to be in how the app handles or transmits firmware updates, potentially exposing sensitive data during the update mechanism.

MitigationUpdate Hideez app to a patched version once available. Until then, avoid using the firmware update feature on untrusted networks.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Hideez app is installed
    On Android device: go to Settings > Apps > look for Hideez app, or run 'adb shell pm list packages | grep hideez'
    Affected if Package com.hideez exists on the device
  2. Determine installed Hideez app version
    On Android: Settings > Apps > Hideez > App info > Version, or run 'adb shell dumpsys package com.hideez | grep versionName'
    Affected if Installed version is 2.7.8.3 or if version cannot be determined but the app is present and was not patched after September 2024
  3. Identify if firmware update feature is configured
    Open Hideez app > navigate to Settings or Device management > look for firmware update, OTA update, or device update options
    Affected if Firmware update feature is present and has been used or enabled on the device
  4. Inspect update traffic on untrusted networks
    Use a network sniffer or proxy (e.g., Burp Suite, Wireshark) while performing a firmware update on the app; check if traffic is unencrypted or passes sensitive data
    Affected if Firmware update traffic is transmitted over HTTP, or sensitive data (credentials, firmware contents) is visible in plaintext on the network

User is affected if Hideez app (com.hideez) version 2.7.8.3 is installed and the firmware update feature is enabled or has been used, especially on untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Hideez app to a patched version once available. Until then, avoid using the firmware update feature on untrusted networks.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-48792 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-48792 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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