dbcve.org
Open IrsApplication · Degamisu

CVE-2024-24757

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-02
Fix available
A fix is available. Upgrade to 1.0.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
open-irs is an issue response robot that reponds to issues in the installed repository. The `.env` file was accidentally uploaded when working with git actions. This problem is fixed in 1.0.1. Discontinuing all sensitive keys and turning into secrets.

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

The open-irs issue response robot accidentally committed its `.env` file containing sensitive environment variables (API keys, credentials, secrets) to the repository through git actions. This exposed all sensitive configuration data publicly, giving attackers access to any services or APIs authenticated by those exposed credentials.

MitigationImmediately rotate all exposed secrets, API keys, and credentials that were in the `.env` file; remove the `.env` from git history using git filter-branch or git-filter-repo; add `.env` to `.gitignore`; and transition to using repository secrets or a secrets manager for future CI/CD workflows.

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
Open IrsApplication
Affected:< 1.0.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

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

  1. Verify if .env file exists in repository
    List all files in the repository root and look for a file named '.env' or check with command: ls -la .env
    Affected if .env file is present in the repository root directory
  2. Check git history for .env commits
    Run 'git log --all --full-history -- .env' or 'git log --all --diff-filter=A -- .env' to see if .env was ever added to the repository
    Affected if git history shows any commits involving .env file
  3. Check for .env in any branch
    Run 'git branch -a' to list all branches, then 'git log --all --oneline -- .env' to search across all branches for .env commits
    Affected if .env appears in commit history of any branch, even if removed later
  4. Inspect .env contents for secrets
    If .env exists, examine its contents for API keys, credentials, tokens, or other sensitive values marked as sensitive
    Affected if .env contains any API keys, passwords, tokens, or credentials
  5. Check installed version of Degamisu Open Irs
    Run 'npm list degamisu-open-irs' or check package.json for the degamisu-open-irs package version
    Affected if Installed version is less than 1.0.1

A user is affected if the .env file was ever committed to the repository (visible in git history) OR if the installed version of Degamisu Open Irs is below 1.0.1, regardless of whether .env was subsequently removed.

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 1.0.1 or later
Fixed in 1.0.1
Interim mitigation

Immediately rotate all exposed secrets, API keys, and credentials that were in the `.env` file; remove the `.env` from git history using git filter-branch or git-filter-repo; add `.env` to `.gitignore`; and transition to using repository secrets or a secrets manager for future CI/CD workflows.

Recommended fix High confidence

1.0.1

  1. Check current installed version of open-irs (e.g., npm list open-irs or pip show open-irs depending on package manager)
  2. Upgrade to version 1.0.1 or later (e.g., npm install open-irs@latest or pip install open-irs==1.0.1)
  3. Rotate all sensitive keys and credentials that may have been exposed in the .env file since the vulnerability allowed accidental exposure of sensitive information
  4. Review git history and remove any accidentally committed .env files or sensitive data from repository history using tools like git-filter-repo or BFG Repo-Cleaner
  5. Ensure .env is added to .gitignore to prevent future commits of sensitive files
Caveat Review release notes for 1.0.1 to confirm no breaking changes in functionality

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

Fix this in Open Irs Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24757 — 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-24757 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