CVE-2018-19153
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 · uneditedparticl through 0.17 (a chain-based proof-of-stake cryptocurrency) allows a remote denial of service. The attacker sends invalid headers/blocks. The attack requires no stake and can fill the victim's disk and RAM.
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 confidenceThe particl cryptocurrency daemon through version 0.17 lacks proper validation of incoming block headers and blocks in its P2P protocol handler. Remote attackers without any stake can send malformed or invalid headers/blocks that consume excessive disk and RAM resources on victim nodes.
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<= 0.17CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Particl daemon is runningCheck running processes for the particl daemon (particld or particl-qt in server mode). On Linux: 'ps aux | grep -i particl' or check systemd service status.Affected if The particl daemon process is currently running on the system.
-
Identify the installed Particl versionRun 'particld --version' or use the RPC command 'particl-cli getinfo' to retrieve the version number. Compare it to the affected range: versions 0.17 and below.Affected if The installed version is 0.17 or any earlier version.
-
Verify P2P networking is enabledCheck the daemon configuration file (particl.conf) for 'listen=1' or 'server=1' settings, or check if the daemon is bound to P2P port (usually 51738 for mainnet). Use 'particl-cli getnetworkinfo' to query P2P status.Affected if P2P networking is enabled and the node accepts incoming connections from the network.
-
Check if inbound connections are allowedReview 'particl.conf' for 'listen=1', 'bind=*', or port configurations. Use 'particl-cli getpeerinfo' to see if inbound peers are connected.Affected if The node accepts inbound P2P connections from untrusted peers.
A user is affected if running Particl daemon version 0.17 or lower with P2P networking enabled, as this allows remote attackers to send malformed headers/blocks that consume excessive resources.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict validation of all incoming headers and blocks before processing, including proof-of-stake verification, structural validation, and resource consumption limits with automatic cleanup of excess data.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19153 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-19153 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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