dbcve.org
IrisApplication · Dfir Iris

CVE-2024-25640

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-19
Fix available
A fix is available. Upgrade to 2.4.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Iris is a web collaborative platform that helps incident responders share technical details during investigations. A stored Cross-Site Scripting (XSS) vulnerability has been identified in iris-web, affecting multiple locations in versions prior to v2.4.0. The vulnerability may allow an attacker to inject malicious scripts into the application, which could then be executed when a user visits the affected locations. This could lead to unauthorized access, data theft, or other related malicious activities. An attacker need to be authenticated on the application to exploit this vulnerability. The issue is fixed in version v2.4.0 of iris-web. No workarounds are available.

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 confidence

Iris-web versions prior to v2.4.0 contain a stored Cross-Site Scripting (XSS) vulnerability affecting multiple locations. An authenticated attacker can inject malicious scripts into the application that persist in the database and execute when other users visit the affected areas, potentially leading to session hijacking, data theft, or unauthorized actions performed in the context of victim users.

MitigationUpgrade to iris-web v2.4.0 or later to remediate this vulnerability. Since no workarounds are available and authentication is required for exploitation, prioritize patching authenticated user input fields and rendering points throughout the application.

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
IrisApplication
Affected:< 2.4.0

CVSS 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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed iris-web version
    Check the version of iris-web currently deployed. This is typically visible in the application interface (often in the footer or About section), or by inspecting the Docker image tag, installation directory, or version file if self-hosted. On command line, you may find this in the iris-web logs, configuration, or by querying the application's API endpoint that returns version info.
    Affected if The installed version is any version prior to v2.4.0 (e.g., v2.3.x, v2.2.x, v2.1.x, etc.)
  2. Verify authentication is enabled
    Confirm that user authentication is required to access the iris-web application. Check whether the login page is enforced and that anonymous access to core functionality is not permitted.
    Affected if Authentication is not properly enforced, or if the application allows unauthenticated access to features that store data in the database
  3. Locate user input fields that store data
    Identify fields in the iris-web interface where authenticated users can submit or upload content that gets stored in the database. Common areas include case names, case descriptions, task fields, evidence metadata, notes, and user profile fields.
    Affected if The application stores user-supplied content in the database and displays it to other users without sanitization

You are affected if your iris-web installation is version 2.4.0 or earlier and authenticated users can input or store content that gets rendered to other users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.4.0 or later
Fixed in 2.4.0
Interim mitigation

Upgrade to iris-web v2.4.0 or later to remediate this vulnerability. Since no workarounds are available and authentication is required for exploitation, prioritize patching authenticated user input fields and rendering points throughout the application.

Recommended fix High confidence

v2.4.0

  1. Obtain the iris-web v2.4.0 release from the official GitHub repository
  2. Review the release notes and changelog for v2.4.0
  3. Backup the current iris-web instance and its database
  4. Deploy iris-web v2.4.0 following the standard installation/upgrade procedure used in your environment
  5. Verify the upgrade was successful by logging in and checking the application version
  6. Test the affected locations mentioned in the vulnerability disclosure to confirm the XSS vulnerability is remediated
Caveat Review release notes for any breaking changes between your current version and v2.4.0 before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Iris Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25640 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25640 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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