RM authorization denial of service via lock abuse
Published Dec 20, 2022 · Updated Apr 16, 2025
Improper input validation in IBM Financial Transaction Manager for SWIFT Services 3.2.4 allows local users to disrupt RM authorization management. IBM has not disclosed which RM authorization input is insufficiently validated or how the product permits one user to lock additional authorizations. Access to the authenticated RM authorization workflow is required, and successful exploitation prevents affected authorizations from being displayed or managed.
Summary
What happened
Improper input validation in IBM Financial Transaction Manager for SWIFT Services 3.2.4 allows local users to disrupt RM authorization management. IBM has not disclosed which RM authorization input is insufficiently validated or how the product permits one user to lock additional authorizations. Access to the authenticated RM authorization workflow is required, and successful exploitation prevents affected authorizations from being displayed or managed.
The record
- CVE
- CVE-2022-43875
- Published
- Dec 20, 2022
- Updated
- Apr 16, 2025
- Vendor
- IBM
- Product
- IBM Financial Transaction Manager for SWIFT Services for Multiplatforms
- Classifications
- CWE-20, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 20, 2022CVE publishedPublication date reported by the CVE source.
- Apr 16, 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=3.2.4
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