Cyber Resilience

CVE-2020-37135

Exposed Creds

Public PoCExposed Creds
Published
07 February 2026
Modified
15 April 2026
CVSS Score v4 9.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0043 35th percentile
Risk Priority 70 floored blend · peak EPSS

Summary

CVE-2020-37135 is a critical-severity Use of Hard-coded Credentials (CWE-798) vulnerability. Its CVSS base score is 9.3 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Default Accounts (T1078.001); ranked at the 35th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-2 (Account Management) and CM-6 (Configuration Settings) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2020-37135 is an authentication bypass vulnerability in AMSS++ 4.7, classified under CWE-798 (use of hard-coded credentials). The flaw allows attackers to access administrative accounts using hardcoded default credentials, specifically the admin username and password '1234', enabling unauthorized administrative access to the system. It carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), indicating high severity due to its network accessibility and confidentiality impact.

Remote attackers require only network access to exploit this vulnerability, with no need for prior privileges, user interaction, or complex preconditions. Successful exploitation grants full administrative access, potentially allowing attackers to view sensitive data, modify configurations, or perform other privileged actions, resulting in high confidentiality impact without integrity or availability disruption.

Advisories and references highlight the backdoor nature of the admin account, with details available at https://www.vulncheck.com/advisories/amss-backdoor-admin-account and a public exploit published at https://www.exploit-db.com/exploits/48114. No specific patch or mitigation steps are detailed in the provided information.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

AMSS++ 4.7 contains an authentication bypass vulnerability that allows attackers to access administrative accounts using hardcoded credentials. Attackers can log in with the default admin username and password '1234' to gain unauthorized administrative access to the system.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1078.001 Default Accounts Stealth
Adversaries may obtain and abuse credentials of a default account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
Why these techniques?

Hardcoded default admin credentials (admin/1234) directly enable use of default accounts for initial unauthorized access.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2025-33089Shared CWE-798
CVE-2026-25803Shared CWE-798
CVE-2026-23781Shared CWE-798
CVE-2026-5667Shared CWE-798
CVE-2024-37630Shared CWE-798
CVE-2025-66237Shared CWE-798
CVE-2026-42929Shared CWE-798
CVE-2026-22312Shared CWE-798
CVE-2026-27785Shared CWE-798
CVE-2026-0622Shared CWE-798

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • IA-5 Authenticator Management
  • AC-2 Account Management
  • CM-6 Configuration Settings
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

IA-5 requires changing default authenticators prior to first use, directly preventing authentication bypass via hardcoded credentials like 'admin/1234'.

prevent

AC-2 mandates management of accounts including disabling unnecessary or default administrative accounts, blocking unauthorized access through hardcoded credentials.

prevent

CM-6 enforces secure configuration settings that prohibit default or hardcoded credentials, mitigating the vulnerability in AMSS++ administrative access.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-01 partial match
prevents

PR.AA-01's credential/key-management processes can reduce the incentive to embed secrets but do not address or detect hard-coded values in source code, so the weakness remains fully possible.

PR.AA-02 none match
prevents

PR.AA-02 addresses human identity proofing and per-person credential issuance at enrollment; it has no bearing on whether developers embed static credentials in software.

PR.DS-01 none match
prevents

PR.DS-01 addresses encryption and integrity of stored data but never touches credential or key management practices, so it neither prevents hard-coded credentials nor removes any of their risk.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Education on secure configuration practices discourages technical staff from embedding or relying on hard-coded credentials in systems and applications.

mitigates

Secure key-generation, distribution and storage procedures reduce the likelihood that hard-coded or default cryptographic keys will be introduced or left unprotected.

prevents

Explicit prohibition of hard-coded passwords and unauthenticated external services stops credentials from being embedded directly in source code.

prevents

Contractual requirements for secure coding practices and evidence of testing make it less likely that hard-coded credentials will be introduced or remain undetected in delivered code.

none

Requiring independent oversight and timely disabling of non-human identities makes it harder for hard-coded or long-lived credentials to remain exploitable.

none

Mandating immediate replacement of vendor-supplied default credentials eliminates the use of hard-coded or factory passwords that attackers can trivially obtain from documentation or firmware.

References