Enterprise Repository vulnerabilitiesRanked by how likely they are to be used.
Enterprise Repository is made by Oracle. We track 21 published vulnerabilities in it, across 2 versions. None of them is on the list of flaws known to be exploited today. If you run Enterprise Repository, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Enterprise Repository vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Enterprise Repository's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Enterprise Repository flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 49%CVE-2020-11998Critical
A regression has been introduced in the commit preventing JMX re-bind.
- 19%CVE-2018-8013Critical
In Apache Batik 1.x before 1.10, when deserializing subclass of `AbstractDocument`, the class takes a string from the inputStream as the class name which then use it to call the no-arg constructor of the class.
- 14%CVE-2019-2904Critical
Vulnerability in the Oracle JDeveloper and ADF product of Oracle Fusion Middleware (component: ADF Faces).
- 13%CVE-2020-11987High
Apache Batik 1.13 is vulnerable to server-side request forgery, caused by improper input validation by the NodePickerPanel.
- 12%CVE-2019-0222High
In Apache ActiveMQ 5.0.0 - 5.15.8, unmarshalling corrupt MQTT frame can lead to broker Out of Memory exception making it unresponsive.
- 11%CVE-2019-17566High
Apache Batik is vulnerable to server-side request forgery, caused by improper input validation by the "xlink:href" attributes.
- 9.8%CVE-2019-0188High
Apache Camel prior to 2.24.0 contains an XML external entity injection (XXE) vulnerability (CWE-611) due to using an outdated vulnerable JSON-lib library.
- 8.0%CVE-2020-11979High
As mitigation for CVE-2020-1945 Apache Ant 1.10.8 changed the permissions of temporary files it created so that only the current user was allowed to access them.
- 7.1%CVE-2020-1941Medium
In Apache ActiveMQ 5.0.0 to 5.15.11, the webconsole admin GUI is open to XSS, in the view that lists the contents of a queue.
- 7.0%CVE-2018-11775High
TLS hostname verification when using the Apache ActiveMQ Client before 5.15.6 was missing which could make the client vulnerable to a MITM attack between a Java application using the ActiveMQ client and the ActiveMQ...
Running Enterprise Repository? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A regression has been introduced in the commit preventing JMX re-bind. By passing an empty environment map to RMIConnectorServer, instead of the map that contains the authentication credentials, it leaves ActiveMQ open to the following attack: https://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html "A remote client could create a javax.management.loading.MLet MBean and use it to create new MBeans from arbitrary URLs, at least if there is no security manager. In other words, a rogue remote client could make your Java application execute arbitrary code." Mitigation: Upgrade to Apache ActiveMQ 5.15.13
- Matched to
- Enterprise Repository on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 21 published vulnerabilities listed under the name Enterprise Repository, across 2 versions.
None of Enterprise Repository's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Enterprise Repository. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.