CVE-2011-2329
First published: Thu Jun 02 2011(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Apache Rampart/c | =1.3.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2011-2329?
CVE-2011-2329 is considered a medium severity vulnerability due to its potential to allow access restriction bypass.
How do I fix CVE-2011-2329?
To fix CVE-2011-2329, upgrade to a version of Apache Rampart/C that is not affected by this vulnerability.
What issue does CVE-2011-2329 exploit?
CVE-2011-2329 exploits a flaw in the timestamp token validation process that allows the use of expired tokens.
Which software versions are affected by CVE-2011-2329?
CVE-2011-2329 specifically affects Apache Rampart/C version 1.3.0.
Can CVE-2011-2329 lead to unauthorized access?
Yes, CVE-2011-2329 can lead to unauthorized access by allowing attackers to use expired timestamp tokens.
- agent/references
- agent/remedy
- agent/softwarecombine
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/last-modified-date
- agent/severity
- agent/weakness
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/apache
- canonical/apache rampart/c
- version/apache rampart/c/1.3.0