Traffic-limit bypass via insufficient transmission control
Published Jul 14, 2022 · Updated Sep 17, 2024
IBM Engineering Lifecycle Optimization - Publishing allows remote authenticated users to transmit more network traffic than permitted. The product does not sufficiently monitor or control transmitted traffic volume, but IBM has not published the affected endpoint or code path. Low-privileged network access is required; affected releases are 6.0.6, 6.0.6.1, 7.0, 7.0.1, and 7.0.2, with impact bounded to excess transmission beyond per-actor limits.
Summary
What happened
IBM Engineering Lifecycle Optimization - Publishing allows remote authenticated users to transmit more network traffic than permitted. The product does not sufficiently monitor or control transmitted traffic volume, but IBM has not published the affected endpoint or code path. Low-privileged network access is required; affected releases are 6.0.6, 6.0.6.1, 7.0, 7.0.1, and 7.0.2, with impact bounded to excess transmission beyond per-actor limits.
The record
- CVE
- CVE-2021-39016
- Published
- Jul 14, 2022
- Updated
- Sep 17, 2024
- Vendor
- IBM
- Product
- IBM Engineering Lifecycle Optimization - Publishing
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 14, 2022CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.0.6
- Affected versionversion=6.0.6.1
- Affected versionversion=7.0
- Affected versionversion=7.0.1
- Affected versionversion=7.0.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo