Engineering Lifecycle Optimization vulnerabilitiesRanked by how likely they are to be used.
Engineering Lifecycle Optimization is made by IBM. We track 11 published vulnerabilities listed under that exact name, across 6 versions. None of them is on the list of flaws known to be exploited today. IBM lists newer releases under their own names, such as Engineering Lifecycle Optimization - Publishing, so check those pages too.
We keep watching the known-exploited list.
Is Engineering Lifecycle Optimization listed under other names? Yes.
IBM also lists Engineering Lifecycle Optimization under more specific names, such as Engineering Lifecycle Optimization - Publishing and Engineering Lifecycle Optimization - Engineering Insights. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Engineering Lifecycle Optimization vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Engineering Lifecycle Optimization's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Engineering Lifecycle Optimization 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.0%CVE-2021-29774High
IBM Jazz Team Server products could allow an authenticated user to obtain elevated privileges under certain configurations.
- 0.7%CVE-2023-45191High
IBM Engineering Lifecycle Optimization 7.0.2 and 7.0.3 uses an inadequate account lockout setting that could allow a remote attacker to brute force account credentials.
- 0.6%CVE-2021-29844High
IBM Jazz Team Server products is vulnerable to server-side request forgery (SSRF).
- 0.6%CVE-2021-29786Medium
IBM Jazz Team Server products stores user credentials in clear text which can be read by an authenticated user.
- 0.5%CVE-2020-5031Medium
IBM Jazz Foundation and IBM Engineering products are vulnerable to cross-site scripting.
- 0.5%CVE-2021-20507Medium
IBM Jazz Foundation and IBM Engineering products are vulnerable to cross-site scripting.
- 0.5%CVE-2021-29673Medium
IBM Jazz Team Server products are vulnerable to cross-site scripting.
- 0.5%CVE-2021-29713Medium
IBM Jazz Team Server products are vulnerable to cross-site scripting.
- 0.4%CVE-2023-45187Medium
IBM Engineering Lifecycle Optimization - Publishing 7.0.2 and 7.0.3 does not invalidate session after logout which could allow an authenticated user to impersonate another user on the system.
- 0.3%CVE-2023-45190Medium
IBM Engineering Lifecycle Optimization 7.0.2 and 7.0.3 is vulnerable to HTTP header injection, caused by improper validation of input by the HOST headers.
Running Engineering Lifecycle Optimization? 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
IBM Jazz Team Server products could allow an authenticated user to obtain elevated privileges under certain configurations. IBM X-Force ID: 203025.
- Matched to
- Engineering Lifecycle Optimization 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 11 published vulnerabilities listed under the name Engineering Lifecycle Optimization, across 6 versions.
None of Engineering Lifecycle Optimization's vulnerabilities is on the list of flaws known to be exploited today.
IBM also lists Engineering Lifecycle Optimization under more specific names, such as Engineering Lifecycle Optimization - Publishing and Engineering Lifecycle Optimization - Engineering Insights. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a EdgeProtect account and track Engineering Lifecycle Optimization. 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.