CVE-2023-51839
Published: 29 January 2024
Summary
CVE-2023-51839 is a critical-severity Use of a Broken or Risky Cryptographic Algorithm (CWE-327) vulnerability in Devicefarmer Smartphone Test Farm. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Network Sniffing (T1040); ranked at the 28.5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-0288
Vulnerability details
DeviceFarmer stf v3.6.6 suffers from Use of a Broken or Risky Cryptographic Algorithm.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
The use of a broken or risky cryptographic algorithm in DeviceFarmer STF v3.6.6 enables adversaries to decrypt intercepted traffic (T1040: Network Sniffing) or perform man-in-the-middle attacks (T1557: Adversary-in-the-Middle) on STF communications for remote Android device management.
Affected Assets
Mitigating Controls
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.
Contacts with security groups provide timely information on broken or risky cryptographic algorithms, reducing the likelihood of their selection and use.
Ongoing education and sharing of recommended practices helps organizations identify and migrate away from broken or risky cryptographic algorithms.
Cross-organization threat feeds commonly include advances in cryptanalysis and active exploits against weak or broken algorithms, allowing organizations to deprecate them proactively.
Capital planning and funding allow selection and ongoing support of strong cryptographic algorithms rather than weak or broken ones.
Risk updates surface newly-broken or risky cryptographic algorithms as threat intelligence and computing advances evolve, enabling timely replacement.
Scanners flag use of broken or weak cryptographic algorithms via known-vulnerability databases.
Enforces approved cryptographic algorithms for each use case, blocking use of broken or risky algorithms.
Flaw remediation replaces broken or risky cryptographic algorithms once safer implementations are released by vendors.