dbcve.org
ZncApplication

CVE-2010-2812

MEDIUM · 5.0 CVSS v2.0 Published 2010-08-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
Client.cpp in ZNC 0.092 allows remote attackers to cause a denial of service (exception and daemon crash) via a PING command that lacks an argument.

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

In ZNC 0.092, Client.cpp fails to validate that the PING command receives an argument before processing. When a remote attacker sends a PING command without the required argument, the code attempts to access a null/missing parameter, triggering an unhandled exception that crashes the daemon.

MitigationUpgrade to ZNC version 0.093 or later which includes the argument validation fix. Alternatively, implement a check in the PING command handler to verify the argument exists before dereferencing.

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
ZncApplication
Affected:= 0.092

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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 ZNC installation and version
    Run 'znc --version' or 'znc -v' to display the installed ZNC version number
    Affected if Version displayed is exactly 0.092
  2. Confirm ZNC daemon is running
    Run 'ps aux | grep znc' or check if the ZNC process is active
    Affected if ZNC is actively running and the version is 0.092
  3. Check ZNC configuration for remote listener
    Examine ZNC config (typically ~/.znc/configs/znc.conf) for any 'Listen' or 'Port' settings that accept remote connections
    Affected if ZNC is configured to accept connections from remote hosts (0.0.0.0 or external IP rather than 127.0.0.1 only)
  4. Test PING command handling if possible
    Connect to the ZNC server and send 'PING' without any argument, observe if the daemon crashes
    Affected if Daemon terminates unexpectedly when PING is sent with no argument and version is 0.092

A system is affected only if ZNC version 0.092 is actively running and accessible remotely, as the crash requires receiving a malformed PING command from a remote attacker.

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

Upgrade to ZNC version 0.093 or later which includes the argument validation fix. Alternatively, implement a check in the PING command handler to verify the argument exists before dereferencing.

Fix this in Znc Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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