SUSE openSUSE Factory up to 0.5.1 obs-scm-bridge link following
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in SUSE openSUSE Factory up to 0.5.1. Impacted is an unknown function of the component obs-scm-bridge. This manipulation causes link following. This vulnerability is tracked as CVE-2024-22038. The attack is restricted to local execution. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability has been found in SUSE openSUSE Factory up to 0.5.1 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component obs-scm-bridge. The manipulation with an unknown input leads to a link following vulnerability. The CWE definition for the vulnerability is CWE-59. The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. As an impact it is known to affect confidentiality. The summary by CVE is:
Various problems in obs-scm-bridge allows attackers that create specially crafted git repositories to leak information of cause denial of service.
The weakness was disclosed by Matthias Gerstner. The advisory is shared at bugzilla.suse.com. This vulnerability is known as CVE-2024-22038 since 01/04/2024. The exploitation appears to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 212314 (SUSE SLED15 / SLES15 / openSUSE 15 Security Update : obs-scm-bridge (SUSE-SU-2024:4212-1)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 0.5.2 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (212314). 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.suse.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.3
CNA Vector (suse): 🔍
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: Link followingCWE: CWE-59
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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 |
Nessus ID: 212314
Nessus Name: SUSE SLED15 / SLES15 / openSUSE 15 Security Update : obs-scm-bridge (SUSE-SU-2024:4212-1)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: openSUSE Factory 0.5.2
Timeline
01/04/2024 🔍11/28/2024 🔍
11/28/2024 🔍
12/11/2024 🔍
Sources
Vendor: suse.comAdvisory: bugzilla.suse.com
Researcher: Matthias Gerstner
Status: Confirmed
CVE: CVE-2024-22038 (🔍)
GCVE (CVE): GCVE-0-2024-22038
GCVE (VulDB): GCVE-100-286357
Entry
Created: 11/28/2024 14:13Updated: 12/11/2024 17:34
Changes: 11/28/2024 14:13 (77), 11/28/2024 19:03 (1), 12/11/2024 17:34 (2)
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.