Apache Helix Front express-session hard-coded password

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Apache Helix Front. It has been declared as problematic. This affects an unknown part of the component express-session. Such manipulation leads to hard-coded password. This vulnerability only affects products that are no longer supported by the maintainer. This vulnerability is listed as CVE-2024-22281. There is no available exploit.
Details
A vulnerability was found in Apache Helix Front (version now known) and classified as problematic. Affected by this issue is some unknown processing of the component express-session. The manipulation with an unknown input leads to a hard-coded password vulnerability. Using CWE to declare the problem leads to CWE-259. The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components. Impacted is confidentiality, integrity, and availability. CVE summarizes:
** UNSUPPORTED WHEN ASSIGNED ** The Apache Helix Front (UI) component contained a hard-coded secret, allowing an attacker to spoof sessions by generating their own fake cookies. This issue affects Apache Helix Front (UI): all versions. As this project is retired, we do not plan to release a version that fixes this issue. Users are recommended to find an alternative or restrict access to the instance to trusted users. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
The advisory is shared for download at seclists.org. This vulnerability is handled as CVE-2024-22281 since 01/08/2024. The exploitation is known to be difficult. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 08/22/2024). The MITRE ATT&CK project declares the attack technique as T1078.001.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
License
Support
Website
- Vendor: https://www.apache.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.2VulDB Meta Temp Score: 6.2
VulDB Base Score: 5.0
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA 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: 🔍
Exploiting
Class: Hard-coded passwordCWE: CWE-259 / CWE-255
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/08/2024 🔍08/20/2024 🔍
08/20/2024 🔍
08/22/2024 🔍
Sources
Vendor: apache.orgAdvisory: seclists.org
Status: Confirmed
CVE: CVE-2024-22281 (🔍)
GCVE (CVE): GCVE-0-2024-22281
GCVE (VulDB): GCVE-100-275288
Entry
Created: 08/20/2024 20:01Updated: 08/22/2024 06:42
Changes: 08/20/2024 20:01 (50), 08/22/2024 06:42 (13)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.