Apache ShenYu 2.4.0/2.4.1 HTTP Response insufficiently protected credentials

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Apache ShenYu 2.4.0/2.4.1 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component HTTP Response Handler. Performing a manipulation results in insufficiently protected credentials. This vulnerability is known as CVE-2022-23223. No exploit is available.
Details
A vulnerability classified as problematic has been found in Apache ShenYu 2.4.0/2.4.1. This affects an unknown part of the component HTTP Response Handler. The manipulation with an unknown input leads to a insufficiently protected credentials vulnerability. CWE is classifying the issue as CWE-522. The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. This is going to have an impact on confidentiality.
The weakness was published 01/25/2022. The advisory is shared at lists.apache.org. This vulnerability is uniquely identified as CVE-2022-23223 since 01/14/2022. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/25/2022). MITRE ATT&CK project uses the attack technique T1552 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
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: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Insufficiently protected credentialsCWE: CWE-522
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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/14/2022 🔍01/25/2022 🔍
01/25/2022 🔍
01/28/2022 🔍
Sources
Vendor: apache.orgAdvisory: lists.apache.org
Status: Confirmed
CVE: CVE-2022-23223 (🔍)
GCVE (CVE): GCVE-0-2022-23223
GCVE (VulDB): GCVE-100-191565
Entry
Created: 01/25/2022 17:24Updated: 01/28/2022 11:15
Changes: 01/25/2022 17:24 (36), 01/28/2022 11:15 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.