ruby193 inclusion of functionality from untrusted control sphere

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.3$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in ruby193. The affected element is an unknown function. This manipulation causes inclusion of functionality from untrusted control sphere. This vulnerability appears as CVE-2013-1945. The attack requires local access. There is no available exploit.

Detailsinfo

A vulnerability has been found in ruby193 (Programming Language Software) (affected version unknown) and classified as problematic. Affected by this vulnerability is an unknown functionality. The manipulation with an unknown input leads to a inclusion of functionality from untrusted control sphere vulnerability. The CWE definition for the vulnerability is CWE-829. The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere. As an impact it is known to affect integrity. The summary by CVE is:

ruby193 uses an insecure LD_LIBRARY_PATH setting.

The weakness was presented 10/31/2019. This vulnerability is known as CVE-2013-1945 since 02/19/2013. The exploitation appears to be easy. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.

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.

Productinfo

Type

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.3
VulDB Meta Temp Score: 3.3

VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 3.3
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Inclusion of functionality from untrusted control sphere
CWE: CWE-829
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

02/19/2013 🔍
10/31/2019 +2445 days 🔍
11/01/2019 +1 days 🔍
02/01/2024 +1553 days 🔍

Sourcesinfo

Advisory: bugzilla.redhat.com
Status: Not defined

CVE: CVE-2013-1945 (🔍)
GCVE (CVE): GCVE-0-2013-1945
GCVE (VulDB): GCVE-100-144733

Entryinfo

Created: 11/01/2019 08:47
Updated: 02/01/2024 10:47
Changes: 11/01/2019 08:47 (31), 11/01/2019 08:52 (18), 02/01/2024 10:47 (3)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!