CVE-2018-19831
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 · uneditedThe ToOwner() function of a smart contract implementation for Cryptbond Network (CBN), an tradable Ethereum ERC20 token, allows attackers to change the owner of the contract, because the function does not check the caller's identity.
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 confidenceThe ToOwner() function in the Cryptbond Network (CBN) ERC20 smart contract lacks an access control check, allowing any external caller to arbitrarily change the contract owner. This is a critical authorization bypass vulnerability where the function directly assigns ownership without verifying the caller's identity.
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 dataall versionsCVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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.
-
Identify if Cryptbond Network contract is deployedQuery the blockchain for any deployed contract matching the CBN ERC20 token standard. Search for contract addresses associated with Cryptbond Network.Affected if A CBN token contract is deployed on any network you monitor or own tokens on.
-
Verify ToOwner() function existsCheck the contract's ABI or interface for a function named 'ToOwner' or 'transferOwnership' that accepts an address parameter. Use blockchain explorers or local contract inspection tools to read the contract metadata.Affected if The deployed contract exposes a ToOwner() function accessible to external callers.
-
Test access control on ToOwner()Attempt to call ToOwner() from a non-ownerEOA (Externally Owned Account) or a different contract address. Submit a transaction with your address as the new owner parameter.Affected if The transaction succeeds and ownership is transferred without requiring the caller to be the current owner.
-
Review contract source code for missing modifiersObtain the contract source code and locate the ToOwner() function definition. Check if it has an access control modifier (e.g., onlyOwner) before the execution logic.Affected if The ToOwner() function lacks an access control modifier and directly assigns ownership.
Your environment is affected if you have deployed the CBN ERC20 token contract and the ToOwner() function can be called successfully by any external caller without ownership verification.
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 dataAdd an appropriate access control modifier (e.g., onlyOwner) to the ToOwner() function to verify the caller is the current contract owner before executing ownership transfer.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19831 — 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-19831 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