CVE-2018-19160
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 · uneditedDiamond through 3.0.1.2 (a chain-based proof-of-stake cryptocurrency) allows a remote denial of service, exploitable by an attacker who acquires even a small amount of stake/coins in the system. The attacker sends invalid headers/blocks, which are stored on the victim's disk.
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 confidenceDiamond proof-of-stake cryptocurrency through version 3.0.1.2 fails to validate headers and blocks before storing them on disk. An attacker who acquires even minimal stake in the network can send invalid headers/blocks that are accepted and persisted, causing disk space exhaustion 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<= 3.0.1.2CVSS 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.
-
Check installed Diamond versionRun 'diamondd --version' or look for version string in the daemon binary, typically found in /usr/bin/diamondd or ~/.diamonddiamond/diamonddAffected if Version is 3.0.1.2 or lower, or if the binary reports a version without validation patches
-
Identify blockchain data directoryCheck the configuration file (diamond.conf) for 'datadir' setting, or look for default location at ~/.diamonddiamond/blocks/ and ~/.diamonddiamond/chainstate/Affected if The datadir contains block and header files from untrusted network peers without validation proof
-
Inspect block storage for unvalidated filesList files in the blocks directory - look for recently added .dat or .blk files that may contain invalid blocks. Use 'ls -lat' to sort by modification time and check for unusually large or many new filesAffected if Large numbers of block files exist that were not cryptographically validated before storage, indicating the vulnerability may have been exploited
-
Check disk usage for abnormal growthRun 'du -sh ~/.diamonddiamond/' or monitor disk usage over time. Compare current blockchain size against expected size for the current block heightAffected if Disk usage is significantly larger than expected for the current chain height, suggesting invalid blocks were stored
-
Verify validation is enabled in configurationReview diamond.conf for any settings related to block/header validation. Look for parameters like 'checkblocks', 'checklevel', or any validation-related flagsAffected if No validation parameters are set, or validation is explicitly disabled, indicating the node accepts blocks without verification
If running Diamond version 3.0.1.2 or lower, the node accepts unvalidated headers and blocks from the network, making it vulnerable to disk space exhaustion attacks.
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 per the consensus rules before accepting and storing them on disk. Reject any headers/blocks that fail cryptographic, format, or consensus rule validation.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19160 — 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-19160 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