# CVE-2018-10239: Privilege escalation in n/a

> A locally authenticated administrator can escalate privileges to super user scope via a weakness in the support access password generation algorithm.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5x64-6cf8-m3mw

## What is CVE-2018-10239?

CVE-2018-10239 is a medium-severity vulnerability in n/a, published on 17 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A privilege escalation vulnerability in the "support access" feature on Infoblox NIOS 6.8 through 8.4.1 could allow a locally authenticated administrator to temporarily gain additional privileges on an affected device and perform actions within the super user scope. The vulnerability is due to a weakness in the "support access" password generation algorithm. A locally authenticated administrative user may be able to exploit this vulnerability if the "support access" feature is enabled, they know the support access code for the current session, and they know the algorithm to generate the support access password from the support access code. "Support access" is disabled by default. When enabled, the access will be automatically disabled (and support access code will expire) after the 24 hours.

Weakness: CWE-264

## Which versions are affected by CVE-2018-10239?

It affects 1 product.


Products: Infoblox Nios.

## How do I fix CVE-2018-10239?

No fix has been published for CVE-2018-10239 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-10239 being exploited?

There is no known exploitation of CVE-2018-10239 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-36046](https://insights.sbomify.com/CVE-2024-36046/): Privilege escalation in n/a (critical 9.8)
- [CVE-2024-36047](https://insights.sbomify.com/CVE-2024-36047/): Other in n/a (critical 9.8)
- [CVE-2024-37566](https://insights.sbomify.com/CVE-2024-37566/): Auth bypass in n/a (critical 9.8)
- [CVE-2024-37567](https://insights.sbomify.com/CVE-2024-37567/): Missing authorization in n/a (critical 9.1)
- [CVE-2025-61880](https://insights.sbomify.com/CVE-2025-61880/): Deserialization in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10239 and fix it if it is affected.

What it is: CVE-2018-10239 is a medium-severity vulnerability in n/a, published on 17 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-10239 in the wild and no public exploit code.

Affected product: n/a. 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-10239/ (Markdown: https://insights.sbomify.com/CVE-2018-10239/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-10239
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-10239
- OSV: https://osv.dev/vulnerability/CVE-2018-10239

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-10239/
Summaries are generated and may contain mistakes; the official description above is the record.