Oracle Agile PLM MCAD Connector 3.3/3.4/3.5/3.6 CAX Client deserialization

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.
9.4$5k-$25k0.00

Summaryinfo

A vulnerability has been found in Oracle Agile PLM MCAD Connector 3.3/3.4/3.5/3.6 and classified as very critical. Affected by this issue is some unknown functionality of the component CAX Client. The manipulation leads to deserialization. This vulnerability is uniquely identified as CVE-2017-5645. The attack is possible to be carried out remotely. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Oracle Agile PLM MCAD Connector 3.3/3.4/3.5/3.6 (Product Lifecycle Management Software). It has been rated as very critical. This issue affects an unknown part of the component CAX Client. The manipulation with an unknown input leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitrary code.

The bug was discovered 04/02/2017. The weakness was disclosed 01/18/2018 by Marcio Almeida as Oracle Critical Patch Update Advisory - January 2018 as confirmed advisory (Website). The advisory is shared at oracle.com. The identification of this vulnerability is CVE-2017-5645 since 01/29/2017. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 01/31/2021).

The vulnerability was handled as a non-public zero-day exploit for at least 15 days. During that time the estimated underground price was around $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 101576 (Fedora 26 : log4j (2017-11edc0d6c3)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 87333 (Oracle WebLogic Server Multiple Vulnerabilities (CPUAPR2018)).

Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (101576) and SecurityFocus (BID 97702†). The entries VDB-99929, VDB-112020, VDB-112034 and VDB-112033 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.8
VulDB Meta Temp Score: 9.7

VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

Vendor Base Score (Oracle): 9.8
Vendor Vector (Oracle): 🔍

NVD Base Score: 9.8
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Deserialization
CWE: CWE-502 / 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 101576
Nessus Name: Fedora 26 : log4j (2017-11edc0d6c3)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 867773
OpenVAS Name: Fedora Update for log4j12 FEDORA-2017-8348115acd
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

01/29/2017 🔍
04/02/2017 +63 days 🔍
04/17/2017 +15 days 🔍
04/17/2017 +0 days 🔍
07/17/2017 +91 days 🔍
01/18/2018 +185 days 🔍
01/18/2018 +0 days 🔍
01/18/2018 +0 days 🔍
01/31/2021 +1109 days 🔍

Sourcesinfo

Vendor: oracle.com

Advisory: Oracle Critical Patch Update Advisory - January 2018
Researcher: Marcio Almeida
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-5645 (🔍)
GCVE (CVE): GCVE-0-2017-5645
GCVE (VulDB): GCVE-100-112157
SecurityFocus: 97702 - Apache Log4j CVE-2017-5645 Remote Code Execution Vulnerability
SecurityTracker: 1040200

See also: 🔍

Entryinfo

Created: 01/18/2018 09:43
Updated: 01/31/2021 23:57
Changes: 01/18/2018 09:43 (91), 12/26/2019 07:04 (1), 01/31/2021 23:57 (2)
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 ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!