Apache CXF 2.4.5/2.5.1 WS-SP UsernameToken Policy improper authentication

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $5k-$25k | 0.00 |
Summary
A vulnerability classified as critical was found in Apache CXF 2.4.5/2.5.1. This affects an unknown part of the component WS-SP UsernameToken Policy. Executing a manipulation of the argument UsernameToken as part of SOAP Request can lead to improper authentication. This vulnerability is handled as CVE-2012-0803. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability classified as critical was found in Apache CXF 2.4.5/2.5.1 (Application Server Software). This vulnerability affects an unknown function of the component WS-SP UsernameToken Policy. The manipulation of the argument UsernameToken as part of a SOAP Request leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
The WS-SP UsernameToken policy in Apache CXF 2.4.5 and 2.5.1 allows remote attackers to bypass authentication by sending an empty UsernameToken as part of a SOAP request.
The bug was discovered 02/07/2012. The weakness was released 08/08/2017 (Website). The advisory is available at marc.info. This vulnerability was named CVE-2012-0803 since 01/19/2012. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 11/04/2019).
The vulnerability was handled as a non-public zero-day exploit for at least 2009 days. During that time the estimated underground price was around $5k-$25k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at OSVDB (78903†). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/19/2012 🔍02/07/2012 🔍
08/08/2017 🔍
08/08/2017 🔍
08/09/2017 🔍
11/04/2019 🔍
Sources
Vendor: apache.orgAdvisory: marc.info
Status: Not defined
Confirmation: 🔍
CVE: CVE-2012-0803 (🔍)
GCVE (CVE): GCVE-0-2012-0803
GCVE (VulDB): GCVE-100-104986
OSVDB: 78903 - CVE-2012-0803 - Apache - CXF - Authentication Bypass Issue
Entry
Created: 08/09/2017 10:37Updated: 11/04/2019 17:35
Changes: 08/09/2017 10:37 (61), 11/04/2019 17:35 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.