Cyber Resilience

CVE-2024-30372

Alltena Allegra ≤ 7.5.1

Published
22 November 2024
Modified
03 January 2025
CVSS Score v3.1 6.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
EPSS Score 0.011 63th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2024-30372 is a medium-severity Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336) vulnerability in Alltena Allegra. Its CVSS base score is 6.3 (Medium).

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

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

Allegra contains a server-side template injection vulnerability in the getLinkText method that permits remote code execution on affected installations. The flaw stems from insufficient validation of user-supplied input before it is processed by the template engine, allowing code execution in the context of the LOCAL SERVICE account. The issue was reported as ZDI-CAN-23609 and carries a CVSS 3.1 score of 6.3.

An authenticated remote attacker can supply a crafted string to the vulnerable method and achieve arbitrary code execution on the target system. No user interaction is required beyond valid credentials, and the attack can be performed over the network with low complexity.

Vendor release notes for Allegra 7.5.2 and the corresponding Zero Day Initiative advisory ZDI-24-1165 address the issue and indicate that an update resolves the template-injection flaw. The EPSS score remains low with negligible movement between its current value of 0.0712 and recorded peak of 0.0722.

EU & UK References

Vulnerability Data

Allegra getLinkText Server-Side Template Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Allegra. Authentication is required to exploit this vulnerability. The specific flaw exists within the implementation of getLinkText method.…

more

The issue results from the lack of proper validation of a user-supplied string before processing it with the template engine. An attacker can leverage this vulnerability to execute code in the context of LOCAL SERVICE. Was ZDI-CAN-23609.

CWE(s)
CWE-1336NVD-CWE-Other

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-5580Same product: Alltena Allegra
CVE-2023-51639Same product: Alltena Allegra
CVE-2025-6216Same product: Alltena Allegra
CVE-2023-52334Same product: Alltena Allegra
CVE-2023-51647Same product: Alltena Allegra
CVE-2025-3486Same product: Alltena Allegra
CVE-2023-52332Same product: Alltena Allegra
CVE-2023-51638Same product: Alltena Allegra
CVE-2025-3485Same product: Alltena Allegra
CVE-2023-51640Same product: Alltena Allegra

Affected Assets

alltena
allegra
≤ 7.5.1

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 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and static analysis can discover missing neutralization of template directives.

SI-10 Information Input Validation good match

Input validation rejects or sanitizes untrusted data before it reaches the template engine, stopping injection of special syntax.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles require use of safe templating APIs and proper escaping of external input.

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