CVE-2018-19165
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 · uneditedneblio through 1.5.1 (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 · moderate confidenceNeblio through 1.5.1 fails to properly validate incoming headers and blocks in its proof-of-stake consensus implementation. An attacker with any stake amount can broadcast invalid headers/blocks which are accepted and written to disk, causing resource exhaustion and denial of service 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<= 1.5.1CVSS 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 Neblio daemon versionRun the version command for the Neblio daemon (e.g., nebliod --version or ./neblio-cli getinfo) and note the version numberAffected if The installed version is 1.5.1 or any version lower than 1.5.1
-
Confirm node is running and network-enabledVerify the Neblio node daemon is actively running and connected to the network (peer count > 0)Affected if The node is online and reachable by peers, as the vulnerability is exploited via incoming headers/blocks from the network
-
Verify proof-of-stake is activeCheck if the wallet has stake capability enabled or if the node is participating in proof-of-stake consensusAffected if Proof-of-stake consensus is enabled, as the vulnerability specifically targets the PoS header/block validation logic
-
Inspect recent headers or blocks for acceptance anomaliesReview node logs or use diagnostic commands to examine recently received headers and blocks for validation failures or unusual acceptance patternsAffected if The node has accepted headers or blocks that should have been rejected under strict consensus validation, or logs show malformed data being written to disk
-
Check for resource exhaustion indicatorsMonitor disk usage, memory consumption, or database growth that might indicate invalid data accumulationAffected if Unusual resource usage patterns suggest the node may have persisted invalid headers/blocks to disk due to missing validation
A Neblio node is affected if it runs version 1.5.1 or lower, is connected to the network with proof-of-stake enabled, and may show signs of accepting invalid headers/blocks or experiencing resource issues from such acceptance.
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 received headers and blocks against consensus rules before accepting or persisting them to disk, rejecting any that fail cryptographic or protocol validation checks.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19165 — 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-19165 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