CVE-2018-19832
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 NETM() function of a smart contract implementation for NewIntelTechMedia (NETM), 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 NETM() function in the NETM ERC20 token smart contract lacks access control validation, allowing any external caller to change the contract owner by invoking this function without authentication.
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 NETM token holdings or interactionsCheck your cryptocurrency wallets or transaction history for any NETM token balances or interactions. Review any dApps or DeFi protocols you use that may interact with NETM tokens.Affected if You hold NETM tokens or have transactions involving the NETM token contract
-
Locate the NETM contract addressCheck your transaction records, wallet token lists, or blockchain explorers (Etherscan for Ethereum-based) for the NETM token contract address you interact with.Affected if The contract address corresponds to the Newinteltechmedia Project deployment
-
Verify contract source code for NETM function access controlIf source code is available on block explorers, locate the NETM() function and check if it has an access control modifier (such as onlyOwner) or require statement validating msg.sender == owner.Affected if The NETM() function has no access control modifier and can be called by any external address
-
Test function accessibility (if you control assets)Use a read-only blockchain call or block explorer to attempt calling the NETM function with a non-owner address. Observe if the transaction succeeds rather than reverting.Affected if The function executes successfully when called by a non-owner address, indicating missing access control
You are affected if you hold or interact with NETM tokens from the Newinteltechmedia Project and the deployed contract has an unprotected NETM() function that allows any caller to change ownership.
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 dataDeploy a new fixed contract with proper ownership access control (e.g., onlyOwner modifier) and migrate all token balances; deprecate the vulnerable contract.
- Consultation6.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,712.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19832 — 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-19832 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