Authentication bypass via CRC-16 credential collisions
Published Jul 28, 2022 · Updated Aug 3, 2024
Broken credential hashing in Honeywell Saia Burgess PG5 PCD products through 2022-05-06 allows attackers to bypass S-Bus authentication. S-Bus authentication accepts a CRC-16 password hash in a write byte message, so an observed hash yields trivial collisions without revealing the password. Passive access to UDP port 5050 traffic is required; successful bypass exposes sensitive control-logic transfer and controller-configuration functions.
Summary
What happened
Broken credential hashing in Honeywell Saia Burgess PG5 PCD products through 2022-05-06 allows attackers to bypass S-Bus authentication. S-Bus authentication accepts a CRC-16 password hash in a write byte message, so an observed hash yields trivial collisions without revealing the password. Passive access to UDP port 5050 traffic is required; successful bypass exposes sensitive control-logic transfer and controller-configuration functions.
The record
- CVE
- CVE-2022-30320
- Published
- Jul 28, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-327, T1040
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 28, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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