Cyber Resilience

CVE-2025-0714

Published
17 February 2025
Modified
15 April 2026
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS Score 0.0016 6th percentile
Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2025-0714 is a medium-severity IV (CWE-1204) vulnerability in Cirosec (inferred from references). Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Weaken Encryption (T1600); ranked at the 6th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

The vulnerability exists in the password storage of Mobateks MobaXterm in versions below 25.0. MobaXTerm uses an initialisation vector (IV) consisting only of zero bytes and a master key to encrypt each password individually. In the default configuration, on opening…

more

MobaXTerm, the user is prompted for their password. A derivative of the password is used as the master key. As both the master key and the IV are the same for each stored password, the AES CFB ciphertext depends only on the plaintext (the password). The static IV and master key make it easier to obtain sensitive information and to decrypt data when it is stored at rest.

CWE(s)
CWE-1204

Related Threats

MITRE ATT&CK Enterprise Techniques

T1600 Weaken Encryption Defense Impairment
Adversaries may compromise a network device’s encryption capability in order to bypass encryption that would otherwise protect data communications.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-25998Shared CWE-1204
CVE-2026-5087Shared CWE-1204
CVE-2023-2747Shared CWE-1204

Affected Assets

Cirosec
—
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)
  • 6 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V11.6.1

Mitigating Controls (NIST 800-53 r5) AI

SC-13 Cryptographic Protection partial match

Requiring and implementing approved cryptography for each use case forces the product to generate IVs that satisfy the primitive's unpredictability and uniqueness requirements.

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 include correct implementation of cryptographic primitives such as IV handling.

PR.DS-01 partial match
prevents

Proper encryption of data-at-rest requires cryptographically sound IV generation.

PR.DS-02 partial match
prevents

Proper encryption of data-in-transit requires cryptographically sound IV generation.

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

Mandates correct use of cryptography, directly requiring strong, unpredictable IV generation for primitives that need it.

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

Security testing in development can detect use of static or predictable IVs before release.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC processes can embed cryptographic standards and reviews that catch weak IV generation.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify cryptographic standards including IV uniqueness and unpredictability.

A.8.28 Secure coding partial match
prevents

Requires secure coding practices that include proper cryptographic API usage and IV handling.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248524 OL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-1204
RHEL 7 (1 rule)
  • V-204497 The Red Hat Enterprise Linux operating system must implement NIST FIPS-validated cryptography for the following: to provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-1204
RHEL 8 (1 rule)
  • V-230223 RHEL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. prevents CWE-1204

References