# CVE-2010-2469: Hardcoded credentials in n/a

> Remote attackers can access Video Recorder data by using the default password for the IEIeMerge account on Linear eMerge devices.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2010
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-g2jm-q5qc-fx6x

## What is CVE-2010-2469?

CVE-2010-2469 is a medium-severity vulnerability in n/a, published on 25 Jun 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Linear eMerge 50 and 5000 uses a default password of eMerge for the IEIeMerge account, which makes it easier for remote attackers to obtain Video Recorder data by establishing a session to the device.

Weakness: CWE-255

## Which versions are affected by CVE-2010-2469?

It affects 2 products.


Products: Linearcorp Emerge 50, Linearcorp Emerge 5000.

## How do I fix CVE-2010-2469?

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

## Is CVE-2010-2469 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-2468](https://insights.sbomify.com/CVE-2010-2468/): Weak cryptography in n/a (critical 10.0)
- [CVE-2010-2465](https://insights.sbomify.com/CVE-2010-2465/): Information disclosure in n/a (medium 5.0)
- [CVE-2010-2466](https://insights.sbomify.com/CVE-2010-2466/): Information disclosure in n/a (medium 5.0)
- [CVE-2010-2467](https://insights.sbomify.com/CVE-2010-2467/): Hardcoded credentials in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2469 and fix it if it is affected.

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

## Sources

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

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