# CVE-2010-2468: Weak cryptography in n/a

> Weak password hashing in S2 Security NetBox allows attackers to recover administrator credentials and gain privileged access.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** 25 Jun 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v7mv-48xw-jjpg

## What is CVE-2010-2468?

CVE-2010-2468 is a critical vulnerability in n/a, published on 25 Jun 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The S2 Security NetBox 2.x and 3.x, as used in the Linear eMerge 50 and 5000 and the Sonitrol eAccess, uses a weak hash algorithm for storing the Administrator password, which makes it easier for context-dependent attackers to obtain privileged access by recovering the cleartext of this password.

Weakness: CWE-310

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

It affects 4 products.


Products: Linearcorp Emerge 50, Linearcorp Emerge 5000, S2sys Netbox, Sonitrol Eaccess.

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

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

## Is CVE-2010-2468 being exploited?

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

## Other vulnerabilities in n/a

- [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)
- [CVE-2010-2469](https://insights.sbomify.com/CVE-2010-2469/): Hardcoded credentials in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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