Agile Engineering Data Management vulnerabilitiesAnd the versions its exploited flaws hit.
Agile Engineering Data Management is made by Oracle. We track 30 published vulnerabilities in it, across 7 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 12 May 2023. If you run Agile Engineering Data Management, check your version against the exploited flaws below and patch those first.
The most recent Agile Engineering Data Management flaw added to the known-exploited list is CVE-2016-8735, on 12 May 2023. We keep watching the known-exploited list.
Which versions of Agile Engineering Data Management do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2016-8735Exploited list, 12 May 2023
Apache Tomcat Remote Code Execution Vulnerability
6.1.36.2.06.2.1.0 - CVE-2020-1938Exploited list, 3 Mar 2022
Apache Tomcat Improper Privilege Management Vulnerability
6.2.1.0
Which Agile Engineering Data Management vulnerabilities are being exploited?
2 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 9.8Apache Tomcat Remote Code Execution Vulnerability
Apache Tomcat contains an unspecified vulnerability that allows for remote code execution if JmxRemoteLifecycleListener is used and an attacker can reach Java Management Extension (JMX) ports.
- 9.8Apache Tomcat Improper Privilege Management Vulnerability
Apache Tomcat treats Apache JServ Protocol (AJP) connections as having higher trust than, for example, a similar HTTP connection.
Which Agile Engineering Data Management 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.
- >99%CVE-2021-45105Medium
Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups.
- >99%
When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat.
- 87%CVE-2020-13935High
The payload length in a WebSocket frame was not correctly validated in Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M1 to 9.0.36, 8.5.0 to 8.5.56 and 7.0.27 to 7.0.104.
- 64%CVE-2020-13934High
An h2c direct connection to Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M5 to 9.0.36 and 8.5.1 to 8.5.56 did not release the HTTP/1.1 processor after the upgrade to HTTP/2.
- 56%CVE-2020-9484High
When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the contents and name of a file on the server; and b) the server...
- 55%CVE-2017-3730High
In OpenSSL 1.1.0 before 1.1.0d, if a malicious server supplies bad parameters for a DHE or ECDHE key exchange then this can result in the client attempting to dereference a NULL pointer leading to a client crash.
- 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-2021-42340High
The fix for bug 63362 present in Apache Tomcat 10.1.0-M1 to 10.1.0-M5, 10.0.0-M1 to 10.0.11, 9.0.40 to 9.0.53 and 8.5.60 to 8.5.71 introduced a memory leak.
Running Agile Engineering Data Management? 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 flaw being exploited affects software Acme tracks
Apache Tomcat contains an unspecified vulnerability that allows for remote code execution if JmxRemoteLifecycleListener is used and an attacker can reach Java Management Extension (JMX) ports. This CVE exists because this listener wasn't updated for consistency with the Oracle patched issues for CVE-2016-3427 which affected credential types.
- Matched to
- Agile Engineering Data Management on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 30 published vulnerabilities listed under the name Agile Engineering Data Management, across 7 versions. The most recent Agile Engineering Data Management flaw added to the known-exploited list is CVE-2016-8735, on 12 May 2023.
2 are on the list of flaws known to be exploited. The most recently added are CVE-2016-8735 and CVE-2020-1938.
Each flaw names its own versions, usually as ranges. The newest, CVE-2016-8735, affects 6.1.3, 6.2.0, 6.2.1.0. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Agile Engineering Data Management. 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.