OpenEXR 2.3.0 IlmThreadPool.cpp ThreadPool resource management

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.
4.3$0-$5k0.00

Summaryinfo

A vulnerability was found in OpenEXR 2.3.0 and classified as problematic. This affects the function ThreadPool of the file IlmBase/IlmThread/IlmThreadPool.cpp. Such manipulation leads to resource management. This vulnerability is listed as CVE-2018-18443. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability was found in OpenEXR 2.3.0. It has been rated as problematic. Affected by this issue is the function ThreadPool of the file IlmBase/IlmThread/IlmThreadPool.cpp. The manipulation with an unknown input leads to a resource management vulnerability. Using CWE to declare the problem leads to CWE-399. Impacted is availability. CVE summarizes:

OpenEXR 2.3.0 has a memory leak in ThreadPool in IlmBase/IlmThread/IlmThreadPool.cpp, as demonstrated by exrmultiview.

The bug was discovered 10/17/2018. The weakness was presented 10/17/2018 (Website). The advisory is available at github.com. This vulnerability is handled as CVE-2018-18443 since 10/17/2018. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

See VDB-125739 for similar entry. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.3

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

NVD Base Score: 4.3
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Resource management
CWE: CWE-399 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

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: 🔍

Upgrade: github.com

Timelineinfo

10/17/2018 🔍
10/17/2018 +0 days 🔍
10/17/2018 +0 days 🔍
10/17/2018 +0 days 🔍
10/18/2018 +1 days 🔍
05/30/2023 +1685 days 🔍

Sourcesinfo

Product: github.com

Advisory: 350
Status: Not defined
Confirmation: 🔍

CVE: CVE-2018-18443 (🔍)
GCVE (CVE): GCVE-0-2018-18443
GCVE (VulDB): GCVE-100-125738
See also: 🔍

Entryinfo

Created: 10/18/2018 07:03
Updated: 05/30/2023 09:34
Changes: 10/18/2018 07:03 (41), 04/05/2020 10:46 (8), 05/30/2023 09:31 (4), 05/30/2023 09:34 (10)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!