Cyber Resilience

CVE-2024-38881

Crypto Weakness in Horizoncloud Caterease 16.0.1.1663 – 24.0.1.2405

Public PoCCrypto Weakness
Published
02 August 2024
Modified
05 July 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0044 36th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2024-38881 is a high-severity Use of a One-Way Hash with a Predictable Salt (CWE-760) vulnerability in Horizoncloud Caterease. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked at the 36th 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 SC-13 (Cryptographic Protection) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

An issue in Horizon Business Services Inc. Caterease 16.0.1.1663 through 24.0.1.2405 and possibly later versions, allows a remote attacker to perform a Rainbow Table Password cracking attack due to the use of one-way hashes without salts when storing user passwords.

CWE(s)
CWE-760

Related Threats

MITRE ATT&CK Enterprise Techniques

T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-38888Same product: Horizoncloud Caterease
CVE-2024-38887Same product: Horizoncloud Caterease
CVE-2024-38883Same product: Horizoncloud Caterease
CVE-2024-38884Same product: Horizoncloud Caterease
CVE-2024-38885Same product: Horizoncloud Caterease
CVE-2024-38886Same product: Horizoncloud Caterease
CVE-2024-38889Same product: Horizoncloud Caterease
CVE-2024-38882Same product: Horizoncloud Caterease
CVE-2024-38890Same product: Horizoncloud Caterease
CVE-2024-38891Same product: Horizoncloud Caterease

Affected Assets

horizoncloud
caterease
16.0.1.1663 — 24.0.1.2405

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

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

Mitigating Controls (NIST 800-53 r5) AI

SC-13 Cryptographic Protection good match

Cryptographic protection requirements can mandate approved algorithms and parameters that include unpredictable salts for password hashing.

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 mostly match
prevents

Secure SDLC practices directly enforce use of unpredictable salts and strong password hashing.

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.

A.8.24 Use of cryptography mostly match
prevents

Use of cryptography requires appropriate cryptographic controls including proper salting, largely mitigating predictable-salt weaknesses.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect weak password hashing implementations.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle includes secure coding practices that would catch predictable-salt usage during design and implementation.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify cryptographic standards that prohibit predictable salts.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture and engineering principles guide the selection of strong cryptographic mechanisms including proper salting.

A.8.28 Secure coding partial match
prevents

Secure coding explicitly prohibits predictable salts and mandates cryptographically secure random salts.

References