# CVE-2010-0550: Auth bypass in n/a

> Remote authenticated users can bypass HTTP Digest Authentication policy by using HTTP Basic Authentication in GNCASTER.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-28w3-369m-84x8

## What is CVE-2010-0550?

CVE-2010-0550 is a medium-severity authentication bypass vulnerability in n/a, published on 4 Feb 2010. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

admin.htm in Geo++ GNCASTER 1.4.0.7 and earlier does not properly enforce HTTP Digest Authentication, which allows remote authenticated users to use HTTP Basic Authentication, bypassing intended server policy.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Geopp Geo\+\+ Gncaster.

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

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

## Is CVE-2010-0550 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-0552](https://insights.sbomify.com/CVE-2010-0552/): Denial of service in n/a (high 7.5)
- [CVE-2010-0554](https://insights.sbomify.com/CVE-2010-0554/): Auth bypass in n/a (high 7.5)
- [CVE-2010-0553](https://insights.sbomify.com/CVE-2010-0553/): Memory corruption in n/a (medium 6.5)
- [CVE-2010-0551](https://insights.sbomify.com/CVE-2010-0551/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-0550 is a medium-severity authentication bypass vulnerability in n/a, published on 4 Feb 2010. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-0550 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-0550/ (Markdown: https://insights.sbomify.com/CVE-2010-0550/index.md)
```

## Sources

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

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