# CVE-2018-12323: Hardcoded credentials in n/a

> Hard-coded root and admin passwords allow physically proximate attackers to gain unauthorized access to Momentum Axel 720P devices.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-r53w-cgff-xvw2

## What is CVE-2018-12323?

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

### Official description

An issue was discovered on Momentum Axel 720P 5.1.8 devices. A password of EHLGVG is hard-coded for the root and admin accounts, which makes it easier for physically proximate attackers to login at the console.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 2 products.


Products: Apollotechnologiesinc Momentum Axel 720p, Apollotechnologiesinc Momentum Axel 720p Firmware.

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

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

## Is CVE-2018-12323 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-12323 is a medium-severity vulnerability in n/a, published on 13 Jun 2018. 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-12323 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-12323/ (Markdown: https://insights.sbomify.com/CVE-2018-12323/index.md)
```

## Sources

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

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