Adjacent-network code execution via untrusted deserialization
Published Jan 22, 2025 · Updated Feb 12, 2025
Untrusted deserialization in IBM Sterling B2B Integrator Standard Edition allows attackers on the local network to execute arbitrary code. IBM has not disclosed the deserialization entry point, serialized format, or code path that processes attacker-controlled data. Network adjacency is required, but authentication and user interaction are not; successful exploitation runs arbitrary code with the service's privileges.
Summary
What happened
Untrusted deserialization in IBM Sterling B2B Integrator Standard Edition allows attackers on the local network to execute arbitrary code. IBM has not disclosed the deserialization entry point, serialized format, or code path that processes attacker-controlled data. Network adjacency is required, but authentication and user interaction are not; successful exploitation runs arbitrary code with the service's privileges.
The record
- CVE
- CVE-2024-31903
- Published
- Jan 22, 2025
- Updated
- Feb 12, 2025
- Vendor
- IBM
- Product
- IBM Sterling B2B Integrator
- Classifications
- CWE-502, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 22, 2025CVE publishedPublication date reported by the CVE source.
- Feb 12, 2025Record 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.0.0 <=6.1.2.5
- Affected versionversion=6.2.0.0 <=6.2.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
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