Remote service interruption via improper input validation
Published Oct 13, 2023 · Updated Sep 16, 2024
Improper input validation in Vrite before 0.3.0 allows remote attackers to interrupt service via crafted network input. The affected validation locus and the specific malformed operation are not disclosed in the CNA record or public patch references. No authentication or user interaction is required, and exploitation can make the service unavailable without reported confidentiality impact.
Summary
What happened
Improper input validation in Vrite before 0.3.0 allows remote attackers to interrupt service via crafted network input. The affected validation locus and the specific malformed operation are not disclosed in the CNA record or public patch references. No authentication or user interaction is required, and exploitation can make the service unavailable without reported confidentiality impact.
The record
- CVE
- CVE-2023-5571
- Published
- Oct 13, 2023
- Updated
- Sep 16, 2024
- Vendor
- Vrite
- Product
- Vrite
- Classifications
- CWE-20, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 13, 2023CVE publishedPublication date reported by the CVE source.
- Sep 16, 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 <0.3.0
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.
Public exploit references
- huntr.dev CVE-2023-5571 proof-of-concept advisoryproof 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