Report disclosure via missing per-report access codes
Published Feb 19, 2021 · Updated Aug 3, 2024
Incorrect authorization in Visualware MyConnection Server before 11.0b build 5382 allows remote attackers to read published reports. The report-publishing subsystem fails to bind each published report to its own access code, so access control does not isolate one report from another. Exploitation requires network access to a published-report endpoint but no authentication or user interaction, and the documented consequence is report disclosure without modification or service interruption.
Summary
What happened
Incorrect authorization in Visualware MyConnection Server before 11.0b build 5382 allows remote attackers to read published reports. The report-publishing subsystem fails to bind each published report to its own access code, so access control does not isolate one report from another. Exploitation requires network access to a published-report endpoint but no authentication or user interaction, and the documented consequence is report disclosure without modification or service interruption.
The record
- CVE
- CVE-2021-27509
- Published
- Feb 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2021CVE 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.
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
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