Database password disclosure via crafted curl request
Published Feb 7, 2024 · Updated May 15, 2025
Hard-coded credentials in SCHUHFRIED 8.22.00 allow remote attackers to obtain the database password through a crafted curl request. Public records do not identify the endpoint or explain how request processing exposes the embedded credential. No authentication or user interaction is required; the documented consequence is disclosure of the database password.
Summary
What happened
Hard-coded credentials in SCHUHFRIED 8.22.00 allow remote attackers to obtain the database password through a crafted curl request. Public records do not identify the endpoint or explain how request processing exposes the embedded credential. No authentication or user interaction is required; the documented consequence is disclosure of the database password.
The record
- CVE
- CVE-2023-38995
- Published
- Feb 7, 2024
- Updated
- May 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-798, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 7, 2024CVE publishedPublication date reported by the CVE source.
- May 15, 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
- SCHUHFRIED pre-authentication exploit technical 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