# CVE-2011-2329: Auth bypass in n/a

> Remote attackers can bypass access restrictions by using expired timestamp tokens due to improper expiration calculation in Apache Rampart C.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **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:** 2 Jun 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xhrx-7gxr-xjcp

## What is CVE-2011-2329?

CVE-2011-2329 is a medium-severity authentication bypass vulnerability in n/a, published on 2 Jun 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The rampart_timestamp_token_validate function in util/rampart_timestamp_token.c in Apache Rampart/C 1.3.0 does not properly calculate the expiration of timestamp tokens, which allows remote attackers to bypass intended access restrictions by leveraging an expired token, a different vulnerability than CVE-2011-0730.

Weakness: CWE-264

## Which versions are affected by CVE-2011-2329?

It affects 1 product.


Products: Apache Rampart\/C.

## How do I fix CVE-2011-2329?

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

## Is CVE-2011-2329 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2329 and fix it if it is affected.

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

## Sources

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

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