# CVE-2012-5309: Auth bypass in n/a

> Remote attackers can bypass authentication restrictions to gain unauthorized access via brute-force attacks against IBM Lotus Notes Traveler.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-pmwv-p724-cpcf

## What is CVE-2012-5309?

CVE-2012-5309 is a medium-severity authentication bypass vulnerability in n/a, published on 8 Oct 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

servlet/traveler in IBM Lotus Notes Traveler through 8.5.3.3 Interim Fix 1 does not properly restrict invalid authentication attempts, which makes it easier for remote attackers to obtain access via a brute-force attack.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2012-5309?

It affects 1 product.


Products: Ibm Lotus Notes Traveler.

## How do I fix CVE-2012-5309?

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

## Is CVE-2012-5309 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-5308](https://insights.sbomify.com/CVE-2012-5308/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2012-4824](https://insights.sbomify.com/CVE-2012-4824/): Open redirect in n/a (medium 5.8)
- [CVE-2009-5032](https://insights.sbomify.com/CVE-2009-5032/): Weak cryptography in n/a (medium 5.8)
- [CVE-2010-4550](https://insights.sbomify.com/CVE-2010-4550/): Denial of service in n/a (medium 5.0)
- [CVE-2010-4552](https://insights.sbomify.com/CVE-2010-4552/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5309 and fix it if it is affected.

What it is: CVE-2012-5309 is a medium-severity authentication bypass vulnerability in n/a, published on 8 Oct 2012. 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-2012-5309 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-2012-5309/ (Markdown: https://insights.sbomify.com/CVE-2012-5309/index.md)
```

## Sources

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

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