CVE-2024-25624
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIris is a web collaborative platform aiming to help incident responders sharing technical details during investigations. Due to an improper setup of Jinja2 environment, reports generation in `iris-web` is prone to a Server Side Template Injection (SSTI). Successful exploitation of the vulnerability can lead to an arbitrary Remote Code Execution. An authenticated administrator has to upload a crafted report template containing the payload. Upon generation of a report based on the weaponized report, any user can trigger the vulnerability. The vulnerability is patched in IRIS v2.4.6. No workaround is available. It is recommended to update as soon as possible. Until patching, review the report templates and keep the administrative privileges that include the upload of report templates limited to dedicated users.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIris-web suffers from a Server Side Template Injection (SSTI) vulnerability due to an improper Jinja2 environment configuration used for report generation. An authenticated administrator can upload a malicious report template containing a Jinja2 payload, and when any user generates a report using this weaponized template, it triggers arbitrary Remote Code Execution on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.4.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Iris versionCheck the Iris-web application version (e.g., via about page, docker image tag, or version file in the installation directory). Compare it against the affected range: versions < 2.4.6 are vulnerable.Affected if Installed version is lower than 2.4.6
-
Verify report template feature is accessibleLog in as an administrator and navigate to the report/template management section. Confirm whether the feature allows uploading custom report templates.Affected if Report template upload feature is enabled and accessible to admin users
-
Audit existing report templates for malicious Jinja2 payloadsAccess the template management interface and review all saved report templates. Look for suspicious Jinja2 syntax such as {{7*7}}, {{config}}, {% for %}, or any template expressions that resemble code execution attempts.Affected if Any existing template contains Jinja2 template expressions beyond basic variable substitution, especially config, os, or code execution patterns
-
Check for unauthorized or unexpected admin accountsReview the user management panel to list all administrator accounts. Verify that only trusted users have admin privileges, particularly those with access to template management.Affected if There are admin accounts that were not created by known trusted personnel, or template management access is granted to untrusted users
You are affected if your Iris version is below 2.4.6 AND the report template upload feature is available to your current admin users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.4.6
Update to IRIS v2.4.6 which contains the patched Jinja2 environment configuration. Until patched, strictly limit administrative privileges for report template uploads to dedicated, trusted users and audit existing templates.
Iris v2.4.6
- Upgrade Iris web application to version 2.4.6 or later
- After upgrading, review existing report templates for any suspicious modifications
- Limit administrative privileges for report template uploads to dedicated, trusted users
- Monitor for any unusual report generation activity
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25624 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-25624 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data