Livecycle Es4 vulnerabilitiesRanked by how likely they are to be used.
Livecycle Es4 is made by Adobe. We track 1 published vulnerability in it, across 0 versions. None of them is on the list of flaws known to be exploited today. If you run Livecycle Es4, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Livecycle Es4 vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Livecycle Es4's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Livecycle Es4 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.
- 1.4%CVE-2023-28500Critical
A Java insecure deserialization vulnerability in Adobe LiveCycle ES4 version 11.0 and earlier allows unauthenticated remote attackers to gain operating system code execution by submitting specially crafted Java...
Running Livecycle Es4? 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 Java insecure deserialization vulnerability in Adobe LiveCycle ES4 version 11.0 and earlier allows unauthenticated remote attackers to gain operating system code execution by submitting specially crafted Java serialized objects to a specific URL. Adobe LiveCycle ES4 version 11.0.1 and later may be vulnerable if the application is installed with Java environment 7u21 and earlier. Exploitation of the vulnerability depends on two factors: insecure deserialization methods used in the Adobe LiveCycle application, and the use of Java environments 7u21 and earlier. The code execution is performed in the context of the account that is running the Adobe LiveCycle application. If the account is privileged, exploitation provides privileged access to the operating system. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
- Matched to
- Livecycle Es4 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 1 published vulnerability listed under the name Livecycle Es4, across 0 versions.
None of Livecycle Es4's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Livecycle Es4. 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.