LiveActive security incident?Get immediate response
CVE Record

CVE-2020-17753: An issue was discovered in function addMeByRC in the smart contract implementation for RC, an Ethereum toke...

An issue was discovered in function addMeByRC in the smart contract implementation for RC, an Ethereum token, allows attackers to transfer an arbitrary amount of tokens to an arbitrary address.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE describes a flaw in an Ethereum token smart contract called RC. The reported issue could let an attacker move any amount of tokens to any address. Business impact depends entirely on whether the organization holds, lists, integrates with, or processes this token.

Executive priority

Treat this as urgent only if the organization has RC token exposure. For unaffected enterprises, priority is low after confirming no holdings, listings, or integrations.

Technical view

The CVE identifies the addMeByRC function in the RC smart contract as allowing arbitrary token transfers to arbitrary addresses. The source bundle provides no CVSS score, CWE, fixed version, verified affected product metadata, or patch details.

Likely exposure

Exposure appears limited to parties with RC token holdings, exchange listings, wallet support, smart-contract integrations, or monitoring responsibilities around the referenced Ethereum addresses. The bundle does not indicate general enterprise software exposure.

Exploitation context

The described capability is severe for token integrity, but the bundle does not cite KEV listing, active exploitation evidence, exploit code, transaction analysis, or remediation confirmation. KEV is false in the supplied data.

Researcher notes

The public record is sparse. Analysis should stay tied to the CVE description and referenced Ethereum addresses. Do not infer affected platforms, root cause, exploit status, or fixes without additional primary evidence.

Mitigation direction

  • Avoid interacting with referenced RC token contracts until risk is verified.
  • Check token maintainer or vendor guidance for migration or fixed-contract instructions.
  • Pause internal listings, integrations, or automated transfers involving RC if exposed.
  • Review custody, exchange, and treasury controls for RC token balances.
  • Communicate potential token-integrity risk to affected business owners.

Validation and detection

  • Inventory wallets, contracts, and integrations for transactions involving referenced addresses.
  • Confirm whether the organization holds, lists, or processes RC tokens.
  • Review Etherscan records for contract identity, token activity, and account exposure.
  • Check internal monitoring for unexpected RC token transfers.
  • Document evidence gaps where source data does not confirm exploit activity.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-17753 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.