dbcve.org
Osprey Pump Controller FirmwareOperating system · Propumpservice

CVE-2023-28718

HIGH · 8.0 CVSS v3.1 Published 2023-03-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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 · unedited
Osprey Pump Controller version 1.01 allows users to perform certain actions via HTTP requests without performing any checks to verify the requests. This may allow an attacker to perform certain actions with administrative privileges if a logged-in user visits a malicious website.

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 · moderate confidence

The Osprey Pump Controller v1.01 lacks anti-CSRF protections on its HTTP endpoints, allowing attackers to craft malicious web pages that can trigger authenticated administrative actions when a legitimate user visits the malicious site while logged in.

MitigationImplement anti-CSRF tokens or referer/same-site cookie validation on all state-changing HTTP requests to prevent unauthorized administrative actions.

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
Osprey Pump Controller FirmwareOperating system
Affected:= 1.01

CVSS 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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the firmware version
    Access the Osprey Pump Controller web interface and check the login page, status page, or system settings for the firmware version. This may also be visible in the HTTP Server header or a dedicated /about or /info endpoint.
    Affected if The version displayed is exactly 1.01 (the affected version)
  2. Verify if login session is required
    Attempt to access administrative functions without authentication. Observe whether the application redirects to a login page or returns an authentication error.
    Affected if The device requires authentication for administrative actions (indicates authenticated attack scenario is possible)
  3. Inspect HTML forms for CSRF tokens
    Log into the web interface and navigate to pages with state-changing forms (e.g., pump control, settings, configuration). View the page source or use browser developer tools to examine each form element. Look for hidden input fields with names like 'csrf_token', 'token', 'nonce', or similar.
    Affected if Forms do not contain any hidden CSRF token fields - the absence of tokens means anti-CSRF protection is missing
  4. Check for SameSite cookie attribute
    After logging in, open browser developer tools and examine the session cookie Set-Cookie headers or the Cookies tab. Check if the session cookie has the SameSite attribute set to 'Strict' or 'Lax'.
    Affected if The session cookie lacks SameSite attribute or has it set to 'None' without Secure flag - indicating no SameSite CSRF protection
  5. Verify CSRF header requirements
    Use a tool like Burp Suite or curl to send a legitimate administrative request (such as changing a setting) and observe whether the server requires a specific header (like X-CSRF-Token) or validates the Referer header.
    Affected if The server accepts state-changing requests without requiring any CSRF-specific headers or Referer validation

A user is affected if they run Osprey Pump Controller Firmware version 1.01 AND the web interface forms lack CSRF tokens and the session cookie lacks SameSite protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens or referer/same-site cookie validation on all state-changing HTTP requests to prevent unauthorized administrative actions.

Fix this in Osprey Pump Controller Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28718 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-28718 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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