CVE-2023-28375
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOsprey Pump Controller version 1.01 is vulnerable to an unauthenticated file disclosure. Using a GET parameter, attackers can disclose arbitrary files on the affected device and disclose sensitive and system information.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOsprey Pump Controller v1.01 contains an unauthenticated file disclosure vulnerability where attackers can use a specially crafted GET parameter to read arbitrary files from the device's filesystem, potentially exposing sensitive configuration files, credentials, and system information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.01CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm the device is Osprey Pump ControllerIdentify the device model by checking the device label, web interface footer, or SNMP/sysinfo output for 'Osprey Pump Controller' or 'Propumpservice'Affected if The device is not an Osprey Pump Controller from Propumpservice - not affected
-
Verify firmware version is 1.01Access the device's web interface admin panel, check the 'About' or 'Status' page, or query the device's sysinfo API/endpoint for the firmware versionAffected if Firmware version is NOT exactly 1.01 - not affected (only version 1.01 is vulnerable)
-
Identify if web interface is exposed without authenticationAttempt to access the device's HTTP/HTTPS web interface from an unauthorized network segment without providing credentialsAffected if The web interface requires no authentication - potentially affected, proceed to next check
-
Check for unauthenticated file access capabilityLocate any web endpoints that accept file path parameters (look for parameters containing 'file', 'path', 'filename', or similar in URL query strings) and attempt to access them without authenticationAffected if An endpoint accepts a GET parameter to specify file paths and returns file contents without authentication - AFFECTED
The environment is affected only if the device is a Propumpservice Osprey Pump Controller running firmware version 1.00 and the web interface with file parameter functionality is exposed without authentication.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict access to the vulnerable endpoint by implementing proper authentication and authorization checks, and sanitize user-supplied input to prevent path traversal attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28375 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-28375 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data