dbcve.org
DogecoinApplication

CVE-2023-30769

CRITICAL · 9.8 CVSS v3.1 Published 2023-04-17
Fix available
A fix is available. Upgrade to 1.14.6 or later.
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
Vulnerability discovered is related to the peer-to-peer (p2p) communications, attackers can craft consensus messages, send it to individual nodes and take them offline. An attacker can crawl the network peers using getaddr message and attack the unpatched nodes.

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

A vulnerability in the peer-to-peer (P2P) consensus communications allows attackers to craft malicious consensus messages that can cause individual nodes to go offline. Attackers can discover network peers by crawling with getaddr messages and target unpatched nodes for denial of service.

MitigationApply vendor patches to all consensus nodes immediately. Consider network segmentation and rate-limiting getaddr messages to reduce attack surface while patches are being deployed.

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
DogecoinApplication
Affected:< 1.14.6

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. Check Dogecoin daemon version
    Run 'dogecoin-cli getnetworkinfo' or 'dogecoind --version' to retrieve the installed version number
    Affected if Version is below 1.14.6 (e.g., 1.14.5, 1.14.4, etc.)
  2. Verify P2P consensus communications are enabled
    Check node configuration and network status. Look for 'listen' parameter in dogecoin.conf or confirm 'listening': true in getnetworkinfo output
    Affected if The node is configured to accept P2P connections (listen mode is enabled)
  3. Confirm node is network-reachable
    Review firewall rules and port configuration. Ensure port 22556 (default Dogecoin P2P) is open to external peers
    Affected if The node accepts incoming P2P connections from the internet or untrusted networks

A node is affected if it runs Dogecoin version below 1.14.6 AND has P2P consensus communications enabled and network-reachable, making it vulnerable to malicious consensus messages causing denial of service.

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.

dbcve · scoped
Upgrade available Upgrade to 1.14.6 or later
Fixed in 1.14.6
Interim mitigation

Apply vendor patches to all consensus nodes immediately. Consider network segmentation and rate-limiting getaddr messages to reduce attack surface while patches are being deployed.

Recommended fix Moderate confidence

Dogecoin Core 1.14.6

  1. 1. Backup your Dogecoin node data and configuration files before starting the upgrade process
  2. 2. Stop the dogecoind service or daemon on the affected node
  3. 3. Download Dogecoin Core version 1.14.6 from the official Dogecoin repository or the official website
  4. 4. Verify the integrity of the downloaded binary using published checksums if available
  5. 5. Replace the existing dogecoind binary with the new version 1.14.6 binary
  6. 6. Restart the dogecoind service or daemon
  7. 7. Verify the running version is 1.14.6 by checking the daemon version (e.g., dogecoin-cli getnetworkinfo)
  8. 8. Monitor the node for正常运行 and ensure it syncs properly with the network

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dogecoin Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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