Sensitive-data access via hardcoded system credentials
Published Nov 4, 2022 · Updated Apr 30, 2025
Hardcoded credentials in BD Totalys MultiProcessor 1.70 and earlier allow local users to access, modify, or delete sensitive data. BD has not disclosed the affected account, credential storage locus, or authentication path beyond confirming that system credentials are embedded and not used directly by customers. Exploitation requires physical access to the instrument or Remote Workstation, Windows credentials or a kiosk escape, and bypass of additional controls.
Summary
What happened
Hardcoded credentials in BD Totalys MultiProcessor 1.70 and earlier allow local users to access, modify, or delete sensitive data. BD has not disclosed the affected account, credential storage locus, or authentication path beyond confirming that system credentials are embedded and not used directly by customers. Exploitation requires physical access to the instrument or Remote Workstation, Windows credentials or a kiosk escape, and bypass of additional controls.
The record
- CVE
- CVE-2022-40263
- Published
- Nov 4, 2022
- Updated
- Apr 30, 2025
- Vendor
- Becton, Dickinson and Company
- Product
- BD Totalys MultiProcessor
- Classifications
- CWE-798
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 4, 2022CVE publishedPublication date reported by the CVE source.
- Apr 30, 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=1.70 <=1.70
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