CVE-2024-36391
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 · uneditedMileSight DeviceHub - CWE-320: Key Management Errors may allow Authentication Bypass and Man-In-The-Middle Traffic
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 confidenceMileSight DeviceHub contains a key management error (CWE-320) where improper handling of cryptographic keys allows attackers to bypass authentication mechanisms and intercept or modify network traffic through man-in-the-middle attacks. This vulnerability stems from weak, default, hardcoded, or improperly stored cryptographic keys used for device authentication and communication encryption.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.0.1-r1CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 DeviceHub versionCheck the installed MileSight DeviceHub version by querying the application or checking system inventory (e.g., dpkg -l, rpm -qi, or the web interface about/status page)Affected if Version is exactly 3.0.1-r1
-
Locate configuration filesSearch for DeviceHub configuration directories and files - typically found in /etc/devicehub, /opt/milesight/devicehub, or the application data directoryAffected if Configuration files exist in default or predictable locations
-
Inspect cryptographic key storageExamine configuration files and key storage locations for embedded cryptographic keys, passwords, or secrets. Look for fields like 'key', 'secret', 'password', 'token', or 'credential' with static valuesAffected if Hardcoded, default, or static values are found for encryption keys or authentication credentials
-
Check key file permissionsReview file permissions on key files or directories containing keys - verify they are not world-readable or group-readableAffected if Key files have weak permissions (e.g., 644, 755, or other permissive settings)
-
Review device communication settingsInspect configuration for device authentication and communication encryption settings - check if TLS/SSL is enforced or if fallback to unencrypted communication is allowedAffected if Encryption is disabled, optional, or weak cipher suites are configured
Affected if MileSight DeviceHub version is exactly 3.0.1-r1 AND hardcoded/default cryptographic keys are present in the configuration, regardless of file permissions.
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 dataImplement proper cryptographic key management including secure key generation, storage, rotation, and distribution; replace any default or hardcoded keys; enforce strong authentication and TLS/encryption for all device communications.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36391 — 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-36391 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