Product Lifecycle Management Software Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Vendor

Identifying all affected vendors is a good starting point for an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Product

Oracle Agile PLM96
Oracle Agile PLM Framework10
Oracle Agile PLM MCAD Connector5
Oracle Agile PLM for Process2
UFIDA PLM1

Grouping vulnerabilities by products helps to get an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Remediation

Official Fix113
Temporary Fix0
Workaround0
Unavailable0
Not Defined2

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High1
Functional0
Proof-of-Concept0
Unproven6
Not Defined108

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical1
Local4
Adjacent2
Network108

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High3
Low43
None69

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required31
None84

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤30
≤46
≤516
≤624
≤726
≤819
≤911
≤1013

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤33
≤46
≤516
≤635
≤718
≤816
≤99
≤1012

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤30
≤46
≤517
≤624
≤725
≤819
≤912
≤1012

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤30
≤44
≤56
≤616
≤725
≤816
≤910
≤1012

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤30
≤40
≤50
≤60
≤72
≤80
≤92
≤100

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤42
≤51
≤63
≤79
≤86
≤94
≤107

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k0
<2k1
<5k5
<10k39
<25k53
<50k9
<100k7
≥100k1

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k70
<2k17
<5k18
<10k3
<25k7
<50k0
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Products (6): Oracle Agile PLM, Oracle Agile PLM for Process, Oracle Agile PLM Framework, Oracle Agile PLM MCAD Connector, Siemens PLM, UFIDA PLM

PublishedBaseTempVulnerabilityProductExpRemCTICVE
10/19/20227.57.2Oracle Agile PLM WebClient denial of serviceAgile PLMNot DefinedOfficial Fix0.03CVE-2020-36518
10/19/20227.57.2Oracle Agile PLM WebClient denial of serviceAgile PLMNot DefinedOfficial Fix0.07CVE-2022-24729
10/19/20227.57.2Oracle Agile PLM Folders/Files/Attachments denial of serviceAgile PLMNot DefinedOfficial Fix0.03CVE-2022-29885
07/19/20226.15.8Oracle Agile PLM Security unknown vulnerabilityAgile PLMNot DefinedOfficial Fix0.00CVE-2021-41184
07/19/20226.46.3Oracle Agile PLM Security cross site scriptingAgile PLMNot DefinedOfficial Fix0.04CVE-2020-11022
07/19/20226.56.3Oracle Agile PLM Security denial of serviceAgile PLMNot DefinedOfficial Fix0.04CVE-2022-23437
07/19/20227.57.3Oracle Agile PLM Security xml external entity referenceAgile PLMNot DefinedOfficial Fix0.03CVE-2020-25649
07/19/20227.57.3Oracle Agile PLM Security information disclosureAgile PLMNot DefinedOfficial Fix0.05CVE-2021-40690
07/19/20228.68.4Oracle Agile PLM Security denial of serviceAgile PLMNot DefinedOfficial Fix0.04CVE-2022-25762
04/19/20224.84.7Oracle Agile PLM Security path traversalAgile PLMNot DefinedOfficial Fix0.05CVE-2021-29425
04/19/20226.36.3Oracle Agile PLM Security cross site scriptingAgile PLMNot DefinedOfficial Fix0.05CVE-2021-41165
04/19/20226.56.3Oracle Agile PLM Attachments information disclosureAgile PLMNot DefinedOfficial Fix0.03CVE-2022-21467
04/19/20226.66.4Oracle Agile PLM MCAD Connector CAX Client input validationAgile PLM MCAD ConnectorNot DefinedOfficial Fix0.04CVE-2021-44832
04/19/20226.66.4Oracle Agile PLM Security input validationAgile PLMNot DefinedOfficial Fix0.02CVE-2021-44832
04/19/20227.57.3Oracle Agile PLM Security denial of serviceAgile PLMNot DefinedOfficial Fix0.03CVE-2021-42340
10/22/20215.55.3UFIDA PLM JBoss command injectionPLMNot DefinedNot Defined0.08CVE-2021-41744
10/19/20215.55.4Oracle Agile PLM Apache Groovy information disclosureAgile PLMNot DefinedOfficial Fix0.02CVE-2020-17521
07/20/20215.95.7Oracle Agile PLM Apache Tomcat information disclosureAgile PLMNot DefinedOfficial Fix0.03CVE-2021-24122
07/20/20216.56.2Oracle Agile PLM CKEditor denial of serviceAgile PLMNot DefinedOfficial Fix0.00CVE-2021-26272
04/21/20217.37.0Oracle Agile PLM Security deserializationAgile PLMNot DefinedOfficial Fix0.00CVE-2019-10086
01/20/20216.15.8Oracle Agile PLM Security cross site scriptingAgile PLMNot DefinedOfficial Fix0.05CVE-2020-9281
01/20/20218.17.7Oracle Agile PLM Security deserializationAgile PLMNot DefinedOfficial Fix0.05CVE-2020-14195
01/19/20215.35.2Oracle Agile PLM Security request smugglingAgile PLMNot DefinedOfficial Fix0.03CVE-2021-33037
01/19/20215.55.4Oracle Agile PLM MCAD Connector CAX Client information disclosureAgile PLM MCAD ConnectorNot DefinedOfficial Fix0.07CVE-2020-17521
01/19/20215.55.4Oracle Agile PLM Security denial of serviceAgile PLMNot DefinedOfficial Fix0.04CVE-2021-36374

90 more entries are not shown

Want to stay up to date on a daily basis?

Enable the mail alert feature now!