Debug-function access via hard-coded credentials
Published Apr 11, 2023 · Updated Feb 11, 2025
Hard-coded credentials in Buffalo BS-GSL and BS-GS switch firmware allow physically proximate attackers to access a debug function. The firmware authenticates access to the debug function with a fixed embedded credential, but its storage location and validation code are undisclosed. Physical access is required, and the documented consequence is limited to debug-function access with low confidentiality impact.
Summary
What happened
Hard-coded credentials in Buffalo BS-GSL and BS-GS switch firmware allow physically proximate attackers to access a debug function. The firmware authenticates access to the debug function with a fixed embedded credential, but its storage location and validation code are undisclosed. Physical access is required, and the documented consequence is limited to debug-function access with low confidentiality impact.
The record
- CVE
- CVE-2023-26588
- Published
- Apr 11, 2023
- Updated
- Feb 11, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-668, CWE-798, T1078
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 11, 2023CVE publishedPublication date reported by the CVE source.
- Feb 11, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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