Cyber Resilience

CVE-2023-6709

Lfprojects Mlflow ≤ 2.9.2

Public PoC
Published
12 December 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0094 58th percentile
Risk Priority 66 floored blend · peak EPSS

Summary

CVE-2023-6709 is a high-severity Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336) vulnerability in Lfprojects Mlflow. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Template Injection (T1221); ranked in the top 42% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

This vulnerability is AI-related — categorised as Other AI Platforms; in the Other ATLAS/OWASP Terms risk domain.

EU & UK References

Vulnerability Data

Improper Neutralization of Special Elements Used in a Template Engine in GitHub repository mlflow/mlflow prior to 2.9.2.

CWE(s)
CWE-1336

AI Security AnalysisAI

AI Category
Other AI Platforms
Risk Domain
Other ATLAS/OWASP Terms
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
MLflow is an open-source platform for managing the machine learning lifecycle, including experiment tracking, reproducibility, deployment, and model registry, fitting under 'Other Platforms'. The vulnerability is a template engine issue (likely SSTI) in this ML platform.

Related Threats

MITRE ATT&CK Enterprise Techniques

T1221 Template Injection Stealth
Adversaries may create or modify references in user document templates to conceal malicious code or force authentication attempts.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-4263Same product: Lfprojects Mlflow
CVE-2024-1560Same product: Lfprojects Mlflow
CVE-2024-37059Same product: Lfprojects Mlflow
CVE-2023-6018Same product: Lfprojects Mlflow
CVE-2023-6974Same product: Lfprojects Mlflow
CVE-2024-3573Same product: Lfprojects Mlflow
CVE-2024-37060Same product: Lfprojects Mlflow
CVE-2024-37055Same product: Lfprojects Mlflow
CVE-2024-37057Same product: Lfprojects Mlflow
CVE-2024-37053Same product: Lfprojects Mlflow

Affected Assets

lfprojects
mlflow
≤ 2.9.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.2
  • V1.3.7
  • V1.3.10

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 require proper input neutralization in template engines to prevent injection.

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.29 Security testing in development and acceptance mostly match
finds

Security testing can detect template-injection flaws but does not itself implement neutralization controls.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and sanitization that directly prevents template-injection weaknesses.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for neutralizing special elements in template engines.

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

Secure architecture principles reduce the likelihood of unsafe template processing but do not prescribe specific neutralization techniques.

A.8.28 Secure coding partial match
prevents

Secure coding standards require proper escaping or sandboxing of template directives, directly mitigating CWE-1336.

References