CVE-2020-10275
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 access tokens for the REST API are directly derived from the publicly available default credentials for the web interface. Given a USERNAME and a PASSWORD, the token string is generated directly with base64(USERNAME:sha256(PASSWORD)). An unauthorized attacker inside the network can use the default credentials to compute the token and interact with the REST API to exfiltrate, infiltrate or delete data.
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 REST API uses a weak token derivation mechanism where tokens are generated as base64(USERNAME:sha256(PASSWORD)) from default web interface credentials. An attacker with knowledge of default credentials can compute valid API tokens and gain unauthorized access to exfiltrate, infiltrate, or delete data.
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<= 2.8.1.1all versionsall versionsall versionsall versionsall versionsall versionsall 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Identify the robot model and firmware versionAccess the robot's web interface or check the system information page. For Mir robots, navigate to Settings > System > About. For Easyrobotics, check the maintenance interface.Affected if The firmware version is Mir100 <= 2.8.1.1, or the model is Mir200, Mir250, Mir500, Mir1000, Er200, Er Lite, or Er Flex (any version)
-
Verify default credentials are still in useAttempt to log into the web interface using common default credentials: admin/admin, administrator/administrator, or the credentials shipped with the device. Also check if the default 'admin' account with default password is active.Affected if The default admin account exists with a default or easily guessable password (such as 'admin', 'password', or blank)
-
Confirm REST API is accessibleCheck if the robot's REST API endpoint is reachable over the network. Try accessing a known API endpoint such as https://[robot-ip]/api/v2/status or similar. Review network exposure settings.Affected if The REST API endpoint is exposed on the network and accepts authentication tokens
-
Inspect authentication token generation methodIf you have access to logs or can generate an API token, examine how tokens are derived. The vulnerable method uses base64(USERNAME:sha256(PASSWORD)). Check if generated tokens match this pattern.Affected if The API uses the weak base64(USERNAME:sha256(PASSWORD)) token derivation instead of proper cryptographic methods like OAuth2 or signed JWTs
-
Review API access logs for suspicious activityExamine the robot's access logs for API calls that may indicate unauthorized token generation or use. Look for repeated API requests from unusual sources.Affected if There are API calls using tokens that can be traced to default credential-derived generation
Your environment is affected if you are running any of the listed Mir or Easyrobotics firmware versions with default credentials still active and the REST API is accessible, particularly if tokens are generated using the base64(USERNAME:sha256(PASSWORD)) method.
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 dataImmediately change all default credentials to strong, unique passwords and implement industry-standard authentication mechanisms (OAuth2, JWT with proper signing) instead of the insecure token derivation method.
- Consultation4.0 h
- Implementation8.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10275 — 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-2020-10275 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