Unauthenticated authorization bypass via HEAD requests
Published Dec 12, 2022 · Updated Apr 22, 2025
Incorrect authorization in Boa Web Server 0.94.13 through 0.94.14 allows remote attackers to bypass Basic Authorization using HEAD requests. The request parser assigns HEAD to M_HEAD, and affected response paths pass that method without enforcing the Basic Authorization constraint. No credentials or user interaction are required, but public sources do not identify the protected operation or data exposed by the bypass.
Summary
What happened
Incorrect authorization in Boa Web Server 0.94.13 through 0.94.14 allows remote attackers to bypass Basic Authorization using HEAD requests. The request parser assigns HEAD to M_HEAD, and affected response paths pass that method without enforcing the Basic Authorization constraint. No credentials or user interaction are required, but public sources do not identify the protected operation or data exposed by the bypass.
The record
- CVE
- CVE-2022-45956
- Published
- Dec 12, 2022
- Updated
- Apr 22, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 12, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 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.
Public exploit references
- Boa Web Server v0.94.14 Authentication Bypassproof of concept · demonstrated
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