Authenticated data disclosure via reported debug exceptions
Published Feb 23, 2022 · Updated Aug 2, 2024
Sensitive information exposure in Microweber before 1.3 allows remote authenticated users to read server and user data in debug mode. The exception handler leaves BadMethodCallException outside its dontReport list, so Laravel processes exception details that can contain sensitive data. An authenticated request and enabled debug mode are required, and the established consequence is disclosure rather than data modification or service interruption.
Summary
What happened
Sensitive information exposure in Microweber before 1.3 allows remote authenticated users to read server and user data in debug mode. The exception handler leaves BadMethodCallException outside its dontReport list, so Laravel processes exception details that can contain sensitive data. An authenticated request and enabled debug mode are required, and the established consequence is disclosure rather than data modification or service interruption.
The record
- CVE
- CVE-2022-0721
- Published
- Feb 23, 2022
- Updated
- Aug 2, 2024
- Vendor
- Microweber
- Product
- Microweber
- Classifications
- CWE-215
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 23, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=unspecified <1.3
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.
Weakness, pattern, technique
Public exploit references
- huntr.dev bounty exploit reportproof of concept · unverified
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