Code InjectionWeakness · CWE-94

CVE-2023-28354

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-09
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
An issue was discovered in Opsview Monitor Agent 6.8. An unauthenticated remote attacker can call check_nrpe against affected targets, specifying known NRPE plugins, which in default installations are configured to accept command control characters and pass them to command-line interpreters for NRPE plugin execution. This allows the attacker to escape NRPE plugin execution and execute commands remotely on the target as NT_AUTHORITY\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 · high confidence

Opsview Monitor Agent 6.8 contains a command injection vulnerability in its NRPE (Nagios Remote Plugin Executor) component. Unauthenticated remote attackers can send specially crafted requests to the NRPE service with command control characters that bypass plugin execution boundaries and get passed directly to the Windows command interpreter, allowing arbitrary code execution as NT_AUTHORITY\SYSTEM.

MitigationRestrict NRPE to only accept pre-defined commands without arguments, disable command variable handling in nrpe.cfg, apply vendor patches, and firewall NRPE ports from untrusted networks.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Confirm Opsview Monitor Agent installation
    Check if Opsview Monitor Agent is installed on the system. On Windows, look for the opsview service via 'Get-Service | Where-Object {$_.DisplayName -like "*Opsview*"}' or check Program Files for opsview directories.
    Affected if Opsview Monitor Agent is present on the system
  2. Identify Opsview version
    Determine the installed Opsview Monitor Agent version. Check the application version through its binary properties, registry entries, or the Programs and Features list. Compare against the affected version 6.8.
    Affected if Installed version is 6.8 or earlier
  3. Verify NRPE service is active
    Check if the NRPE (Nagios Remote Plugin Executor) service is running. On Windows, run 'Get-Service -Name nrpe' or check if port 5666 (default NRPE port) is listening via 'netstat -an | findstr 5666'.
    Affected if NRPE service is running and listening on its port
  4. Examine NRPE configuration for command argument handling
    Locate and review the nrpe.cfg configuration file (typically in the Opsview agent etc directory). Search for directives like 'dont_blame_nrpe' or any command definitions that permit arguments.
    Affected if NRPE is configured to accept commands with arguments (dont_blame_nrpe=1 or similar)
  5. Assess NRPE network exposure
    Review firewall rules and network configuration to determine if the NRPE port is accessible from untrusted network segments. Check if NRPE port 5666 is bound to non-localhost interfaces.
    Affected if NRPE port is accessible from untrusted networks or bound to external interfaces

A system is affected if Opsview Monitor Agent version 6.8 is installed with NRPE service running and accessible, especially if NRPE accepts command arguments or is exposed to untrusted networks.

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

Restrict NRPE to only accept pre-defined commands without arguments, disable command variable handling in nrpe.cfg, apply vendor patches, and firewall NRPE ports from untrusted networks.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-28354 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-28354 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