Cyber Resilience

CVE-2020-37168

Crypto Weakness

Public PoCCrypto Weakness
Published
13 May 2026
Modified
17 June 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.0025 16th percentile
Risk Priority 70 floored blend · peak EPSS

Summary

CVE-2020-37168 is a critical-severity Use of Weak Hash (CWE-328) vulnerability in Systempay (inferred from references). Its CVSS base score is 9.3 (Critical).

Operationally, ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Ecommerce Systempay 1.0 contains a weak cryptographic implementation vulnerability that allows attackers to brute force the 16-character production secret key used for payment signature generation. Attackers can extract payment form data and signatures from POST requests to the payment endpoint,…

more

then use SHA1 hash comparison to iteratively test key candidates until discovering the correct production key, enabling them to forge valid payment signatures and manipulate transaction amounts.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-41879Shared CWE-328
CVE-2024-23589Shared CWE-328
CVE-2024-47829Shared CWE-328
CVE-2024-48924Shared CWE-328
CVE-2025-54535Shared CWE-328
CVE-2025-47276Shared CWE-328
CVE-2025-41256Shared CWE-328
CVE-2026-44582Shared CWE-328
CVE-2024-54143Shared CWE-328
CVE-2024-34914Shared CWE-328

Affected Assets

Systempay
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 5 hardening rules · 5 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V11.2.3
  • V6.5.2

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-328

Requires appropriate hash functions for cryptographic uses, preventing reliance on weak hashes.

addresses: CWE-328

Security updates supplant weak hashing algorithms with stronger alternatives before attackers can exploit the original weakness.

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.PS-06 full match
prevents

Secure-SDLC requirements explicitly forbid weak cryptographic algorithms, fully preventing CWE-328 while covering only one aspect of development practice.

PR.DS-01 mostly match
prevents

Proper data-at-rest integrity protection requires strong cryptographic hashes, directly blocking weak-hash usage.

PR.DS-02 mostly match
prevents

Data-in-transit integrity likewise depends on strong hashes, so the control prevents the weakness while the weakness only partially satisfies the outcome.

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

Mandates use of approved cryptographic algorithms, directly preventing weak-hash selection.

detects

Security testing can detect weak-hash usage but does not prescribe algorithm choice.

prevents

Application security requirements can specify strong hashing, but the control is broader.

prevents

Requires secure coding standards that forbid weak hash functions in source code.

References