# CVE-2010-5291: Security feature bypass in n/a

> Remote attackers can bypass login blacklisting to brute-force credentials and gain unauthorized access to the Amberdms Billing System.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 10 Jan 2014
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-576c-c7pp-5jg8

## What is CVE-2010-5291?

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

### Official description

Amberdms Billing System (ABS) before 1.4.1 does not properly implement blacklisting after detection of invalid login attempts, which makes it easier for remote attackers to obtain access via a brute-force approach.

Weakness: CWE-264

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

It affects 1 product.


Products: Amberdms Amberdms Billing System.

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

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

## Is CVE-2010-5291 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-5292](https://insights.sbomify.com/CVE-2010-5292/): Information disclosure in n/a (low 1.9)

## Fix prompt for AI coding agents

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

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

## Sources

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

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