Oracle PeopleSoft Enterprise PeopleTools 8.55/8.56/8.57 PIA Core Technology Local Privilege Escalation

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

Summaryinfo

A vulnerability identified as critical has been detected in Oracle PeopleSoft Enterprise PeopleTools 8.55/8.56/8.57. This issue affects some unknown processing of the component PIA Core Technology. The manipulation leads to an unknown weakness. This vulnerability is traded as CVE-2019-2637. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in Oracle PeopleSoft Enterprise PeopleTools 8.55/8.56/8.57 (Enterprise Resource Planning Software) and classified as critical. This issue affects some unknown functionality of the component PIA Core Technology. Impacted is confidentiality, and integrity.

The weakness was shared 04/16/2019 as Oracle Critical Patch Update Advisory - April 2019 as confirmed advisory (Website). The advisory is shared at oracle.com. The identification of this vulnerability is CVE-2019-2637. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.

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

The entries VDB-133580, VDB-133572, VDB-133573 and VDB-133574 are related to this item. 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: 6.1
VulDB Meta Temp Score: 5.9

VulDB Base Score: 6.1
VulDB Temp Score: 5.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

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

CVSSv2info

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

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

Exploitinginfo

Class: Local Privilege Escalation
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
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: Upgrade
Status: 🔍

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

Timelineinfo

12/14/2018 🔍
04/16/2019 +123 days 🔍
04/16/2019 +0 days 🔍
04/18/2019 +2 days 🔍
09/03/2023 +1599 days 🔍

Sourcesinfo

Vendor: oracle.com

Advisory: Oracle Critical Patch Update Advisory - April 2019
Status: Confirmed

CVE: CVE-2019-2637 (🔍)
GCVE (CVE): GCVE-0-2019-2637
GCVE (VulDB): GCVE-100-133709
See also: 🔍

Entryinfo

Created: 04/18/2019 07:39
Updated: 09/03/2023 17:44
Changes: 04/18/2019 07:39 (49), 09/03/2023 17:44 (7)
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 ▸

Want to know what is going to be exploited?

We predict KEV entries!