Payment-card disclosure via sensitive logcat entries
Published Nov 7, 2023 · Updated Sep 5, 2024
Insecure logging in OPay 1.5.1.26 for Android allows attackers with log access to read payment-card details and CVV codes. The application writes sensitive payment-card data, including CVV codes, to Android logcat instead of excluding it from diagnostic output. Exposure requires access to the affected device's logcat output; published evidence does not establish disclosure of other account data.
Summary
What happened
Insecure logging in OPay 1.5.1.26 for Android allows attackers with log access to read payment-card details and CVV codes. The application writes sensitive payment-card data, including CVV codes, to Android logcat instead of excluding it from diagnostic output. Exposure requires access to the affected device's logcat output; published evidence does not establish disclosure of other account data.
The record
- CVE
- CVE-2021-43419
- Published
- Nov 7, 2023
- Updated
- Sep 5, 2024
- Vendor
- OPay Digital Services Limited
- Product
- OPay
- Classifications
- CWE-778, T1533
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 7, 2023CVE publishedPublication date reported by the CVE source.
- Sep 5, 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=1.5.1.26
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.
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