CVE intelligence and bounded remediation

CVE-2020-10275 — The access tokens for the REST API are directly derived from the publicly available default credentials for the web interface

Critical CVSS 9.8

The 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.

Severity
Critical
CVSS
9.8 (3.1)
Published
2020-06-24
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-261, CWE-326

Affected products

  • mobile-industrial-robots / mir100_firmware
  • mobile-industrial-robots / mir200_firmware
  • mobile-industrial-robots / mir250_firmware
  • mobile-industrial-robots / mir500_firmware
  • mobile-industrial-robots / mir1000_firmware
  • easyrobotics / er200_firmware

Showing 6 representative product identities from 10 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Cryptography, certificate, signature, and channel validation

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Inventory affected algorithms, key uses, trust stores, certificate validation settings, random sources, and plaintext channels across clients and services.
  • Determine which secrets, identities, signatures, or data protections depend on the affected primitive or validation path.
  • Check debug, compatibility, fallback, and hostname or audience override settings in build and runtime configuration.

Remediate safely

  • Use a maintained platform cryptographic API with approved algorithms, modes, parameters, randomness, and full peer identity validation.
  • Remove insecure fallback and validation bypasses; separate keys by purpose and load them from managed secret storage.
  • Plan rotation or reissuance for affected keys, certificates, tokens, hashes, or ciphertext and document compatibility sequencing.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.