CVE-2018-6662 SB10232 - McAfee Management of Native Encryption (MNE) - Privilege Escalation vulnerability
High 7.5
Published
Updated
Check this codebase for CVE-2018-6662 and fix it if it is affected.
What it is: CVE-2018-6662 is a high-severity vulnerability in McAfee Management of Native Encryption (MNE), published on 5 Jun 2018.
Exploitation: There is no known exploitation of CVE-2018-6662 in the wild and no public exploit code.
Affected product: McAfee Management of Native Encryption (MNE). 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-2018-6662/ (Markdown: https://insights.sbomify.com/CVE-2018-6662/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2018-6662?
CVE-2018-6662 is a high-severity vulnerability in McAfee Management of Native Encryption (MNE), published on 5 Jun 2018.
Official description
Privilege Escalation vulnerability in McAfee Management of Native Encryption (MNE) before 4.1.4 allows local users to gain elevated privileges via a crafted user input.
Weakness: CWE-78
Which versions are affected by CVE-2018-6662?
It affects 1 product.
Products include Mcafee Management of Native Encryption.
How do I fix CVE-2018-6662?
No fix has been published for CVE-2018-6662 yet. Limit exposure of the affected software until one is available.
Is CVE-2018-6662 being exploited?
There is no known exploitation of CVE-2018-6662 in the wild and no public exploit code.
Sources
Also known as GHSA-6chj-cqj2-4qmr.