# CVE-2019-17240: Security feature bypass in n/a

> Attackers can bypass brute-force protection in Bludit by spoofing IP headers, allowing unlimited login attempts.

- **Severity:** Low 3.7 (`CVSS:3.0/AC:H/AV:N/A:N/C:L/I:N/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9pgc-3hv6-jch2

## What is CVE-2019-17240?

CVE-2019-17240 is a low-severity vulnerability in n/a, published on 6 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

bl-kernel/security.class.php in Bludit 3.9.2 allows attackers to bypass a brute-force protection mechanism by using many different forged X-Forwarded-For or Client-IP HTTP headers.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2019-17240?

It affects 1 product.


Products: Bludit Bludit.

## How do I fix CVE-2019-17240?

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

## Is CVE-2019-17240 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-17240 exists.

Public exploit code:

- This is the exploit of CVE-2019-17240.  (github_poc): https://github.com/pingport80/CVE-2019-17240
- Bludit <= 3.9.2 - Authentication Bruteforce Mitigation Bypass Exploit/PoC (github_poc): https://github.com/ColdFusionX/CVE-2019-17240_Bludit-BF-Bypass
- https://github.com/spyx/cve-2019-17240 (github_poc): https://github.com/spyx/cve-2019-17240
- Bludit 3.9.2 - Auth Bruteforce Bypass CVE:2019-17240 Refurbish In bash (github_poc): https://github.com/0xDTC/Bludit-3.9.2-Auth-Bruteforce-Bypass-CVE-2019-17240
- Bludit 3.9.2 - bruteforce bypass - CVE-2019-17240 (github_poc): https://github.com/LucaReggiannini/Bludit-3-9-2-bb
- Better version of rastating.github.io/bludit-brute-force-mitigation-bypass/ (github_poc): https://github.com/triple-octopus/Bludit-CVE-2019-17240-Fork

## Other vulnerabilities in n/a

- [CVE-2020-18879](https://insights.sbomify.com/CVE-2020-18879/): File upload in n/a (critical 9.8)
- [CVE-2020-20495](https://insights.sbomify.com/CVE-2020-20495/): Path traversal in n/a (critical 9.1)
- [CVE-2020-18190](https://insights.sbomify.com/CVE-2020-18190/): Path traversal in n/a (critical 9.1)
- [CVE-2024-24550](https://insights.sbomify.com/CVE-2024-24550/): Bludit - Remote Code Execution (RCE) through File API (high 8.9)
- [CVE-2024-24551](https://insights.sbomify.com/CVE-2024-24551/): Bludit - Remote Code Execution (RCE) through Image API (high 8.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-17240 and fix it if it is affected.

What it is: CVE-2019-17240 is a low-severity vulnerability in n/a, published on 6 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-17240 exists.

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-2019-17240/ (Markdown: https://insights.sbomify.com/CVE-2019-17240/index.md)
```

## Sources

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

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