# CVE-2017-9090: Security feature bypass in n/a

> Attackers can bypass CAPTCHA verification in Allen Disk by submitting an empty captcha field, allowing automated abuse of registration.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 19 May 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-fhph-5g4h-87mq

## What is CVE-2017-9090?

CVE-2017-9090 is a high-severity vulnerability in n/a, published on 19 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

reg.php in Allen Disk 1.6 doesn't check if isset($_SESSION['captcha']['code'])==1, which makes it possible to bypass the CAPTCHA via an empty $_POST['captcha'].

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-9090?

It affects 1 product.


Products: Allen Disk Project Allen Disk.

## How do I fix CVE-2017-9090?

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

## Is CVE-2017-9090 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9091](https://insights.sbomify.com/CVE-2017-9091/): Security feature bypass in n/a (high 7.5)
- [CVE-2017-9307](https://insights.sbomify.com/CVE-2017-9307/): Server-side request forgery in n/a (medium 6.5)
- [CVE-2017-8848](https://insights.sbomify.com/CVE-2017-8848/): Cross-site request forgery in n/a (medium 6.5)
- [CVE-2017-8832](https://insights.sbomify.com/CVE-2017-8832/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2017-9249](https://insights.sbomify.com/CVE-2017-9249/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9090 and fix it if it is affected.

What it is: CVE-2017-9090 is a high-severity vulnerability in n/a, published on 19 May 2017. 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-2017-9090 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-2017-9090/ (Markdown: https://insights.sbomify.com/CVE-2017-9090/index.md)
```

## Sources

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

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