CVE-2011-2329
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Application impact
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| apache | rampart\/c | 1.3.0 | |
References
- 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
- 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
- https://launchpad.net/ubuntu/+source/rampart/+changelog
CWEs
CWE-264
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.