dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-2882

CRITICAL · 9.3 CVSS v4.0 Published 2024-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
SDG Technologies PnPSCADA allows a remote attacker to attach various entities without requiring system authentication. This breach could potentially lead to unauthorized control, data manipulation, and access to sensitive information within the SCADA system.

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

SDG Technologies PnPSCADA contains an authentication bypass vulnerability allowing unauthenticated remote attackers to attach various entities to the system. This enables unauthorized control operations, data manipulation, and access to sensitive SCADA information without any credentials.

MitigationApply vendor-supplied patch for CVE-2024-2882 immediately. Until patch is available, implement network segmentation to restrict access to SCADA interfaces and deploy additional authentication layers such as VPN or jump host for operational technology network access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm PnPSCADA installation
    Inventory your systems for SDG Technologies PnPSCADA software. Check installed programs on Windows systems via Programs and Features, or search for PnPSCADA processes/services running on the host using tasklist or Get-Process commands.
    Affected if SDG Technologies PnPSCADA is installed and running in the environment
  2. Identify PnPSCADA version
    Locate the PnPSCADA version information. Check the application directory for version files, or run 'pnpscada -v' or similar version command if available. Also check the Windows registry under HKLM\Software\SDG Technologies or HKLM\Software\Wow6432Node\SDG Technologies for the installed version.
    Affected if The installed version cannot be determined or is any version of PnPSCADA prior to vendor patch application
  3. Assess SCADA interface exposure
    Identify network listeners for PnPSCADA web interfaces, REST APIs, or OPC ports. Use netstat -an | grep <port> or scan the host with nmap to find ports typically used by SCADA systems (often 80, 443, or custom ports like 8080, 48484).
    Affected if SCADA web interfaces or APIs are listening on network-accessible IP addresses without VPN or jump host protection
  4. Verify authentication enforcement
    Test the PnPSCADA login page or API endpoints by attempting unauthenticated access. Observe whether the system returns authenticated session data, allows entity enumeration, or permits control operations without presenting valid credentials.
    Affected if Unauthenticated requests to SCADA interfaces succeed in returning sensitive data, control options, or system entity information without authentication tokens
  5. Review entity attachment logs
    Examine PnPSCADA audit logs, event logs, or security logs for unexpected entity attachments, new device registrations, or unauthorized control operations. Look for entries with no associated user authentication or from unexpected source IPs.
    Affected if Logs show entity attachments, device registrations, or control commands originating from unauthenticated or unexpected IP addresses

If PnPSCADA is installed and its interfaces are network-accessible without VPN or additional authentication, the environment is likely affected by this authentication bypass vulnerability.

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

Apply vendor-supplied patch for CVE-2024-2882 immediately. Until patch is available, implement network segmentation to restrict access to SCADA interfaces and deploy additional authentication layers such as VPN or jump host for operational technology network access.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA12.0 h
60.0 hours of engineering $10,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2882 — 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-2024-2882 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