Apache Sling JCR Base up to 3.1.11 RepositoryAccessor getRepository/getRepositoryFromURL injection

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Apache Sling JCR Base up to 3.1.11. This affects the function getRepository/getRepositoryFromURL of the component RepositoryAccessor. The manipulation results in injection.
This vulnerability is reported as CVE-2023-25141. The attack can be launched remotely. No exploit exists.
Upgrading the affected component is recommended.
Details
A vulnerability classified as critical has been found in Apache Sling JCR Base up to 3.1.11. Affected is the function getRepository/getRepositoryFromURL of the component RepositoryAccessor. The manipulation with an unknown input leads to a injection vulnerability. CWE is classifying the issue as CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
Apache Sling JCR Base < 3.1.12 has a critical injection vulnerability when running on old JDK versions (JDK 1.8.191 or earlier) through utility functions in RepositoryAccessor. The functions getRepository and getRepositoryFromURL allow an application to access data stored in a remote location via JDNI and RMI. Users of Apache Sling JCR Base are recommended to upgrade to Apache Sling JCR Base 3.1.12 or later, or to run on a more recent JDK.
The weakness was disclosed 02/14/2023. The advisory is shared for download at sling.apache.org. This vulnerability is traded as CVE-2023-25141 since 02/03/2023. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1055.
Upgrading to version 3.1.12 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
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: 6.9VulDB Meta Temp Score: 6.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: 🔍
Exploiting
Class: InjectionCWE: CWE-74 / CWE-707 / CWE-20
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Sling JCR Base 3.1.12
Timeline
02/03/2023 🔍02/14/2023 🔍
02/14/2023 🔍
03/12/2023 🔍
Sources
Vendor: apache.orgAdvisory: sling.apache.org
Status: Confirmed
CVE: CVE-2023-25141 (🔍)
GCVE (CVE): GCVE-0-2023-25141
GCVE (VulDB): GCVE-100-220932
Entry
Created: 02/14/2023 14:43Updated: 03/12/2023 15:18
Changes: 02/14/2023 14:43 (40), 03/12/2023 15:18 (11)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.