Critical severity · published Oct 25, 2016
CVE-2016-5599
Unspecified vulnerability in the Oracle Advanced Supply Chain Planning component in Oracle Supply Chain Products Suite 12.2.3 through 12.2.5 allows remote attackers to affect…
9.1
CVSS
2%
EPSS
No
On KEV
Description
Unspecified vulnerability in the Oracle Advanced Supply Chain Planning component in Oracle Supply Chain Products Suite 12.2.3 through 12.2.5 allows remote attackers to affect confidentiality and integrity via vectors related to MscObieeSrvlt.
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)2.0% · higher than 80% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
AS
Advanced Supply Chain Planning · Oracle
12.2.3; 12.2.4; 12.2.5 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2016-5599
CVE.org
https://www.cve.org/CVERecord?id=CVE-2016-5599
Patch
http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html
www.securityfocus.com
http://www.securityfocus.com/bid/93619
More from Advanced Supply Chain Planning
9.8
CVE-2022-23305
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout
9.1
CVE-2021-2253
Vulnerability in the Oracle Advanced Supply Chain Planning product of Oracle Supply Chain (component: Core)
8.8
CVE-2022-23307
CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw
8.8
CVE-2022-23302
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration…
7.5
CVE-2021-4104
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration