CVE-2024-36391 MileSight DeviceHub - CWE-320: Key Management Errors
Critical 9.1
Published
Updated
Check this codebase for CVE-2024-36391 and fix it if it is affected.
What it is: CVE-2024-36391 is a critical vulnerability in MileSight DeviceHub, published on 2 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-36391 in the wild and no public exploit code.
Affected product: MileSight DeviceHub. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2024-36391/ (Markdown: https://insights.sbomify.com/CVE-2024-36391/index.md)
Key management errors in MileSight DeviceHub allow authentication bypass and man-in-the-middle traffic interception.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-36391?
CVE-2024-36391 is a critical vulnerability in MileSight DeviceHub, published on 2 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
MileSight DeviceHub - CWE-320: Key Management Errors may allow Authentication Bypass and Man-In-The-Middle Traffic
Weakness: CWE-320
Which versions are affected by CVE-2024-36391?
It affects 1 product.
Products include Milesight Devicehub.
How do I fix CVE-2024-36391?
No fix has been published for CVE-2024-36391 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-36391 being exploited?
There is no known exploitation of CVE-2024-36391 in the wild and no public exploit code.
Other vulnerabilities in MileSight DeviceHub
- CVE-2024-36388 MileSight DeviceHub - CWE-305 Missing Authentication for Critical Function
- CVE-2024-27776 MileSight DeviceHub - CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE-2024-36389 MileSight DeviceHub - CWE-330 Use of Insufficiently Random Values
- CVE-2024-36390 MileSight DeviceHub - CWE-20 Improper Input Validation
- CVE-2024-36392 MileSight DeviceHub - CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Sources
Also known as GHSA-5h7p-2q7c-v7w8.