dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-39327

CRITICAL · 9.9 CVSS v3.1 Published 2025-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
Incorrect Access Control vulnerability in Atos Eviden IDRA before 2.6.1 could allow the possibility to obtain CA signing in an illegitimate way.

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

Atos Eviden IDRA before version 2.6.1 contains an Incorrect Access Control vulnerability that allows unauthorized actors to obtain CA (Certificate Authority) signing operations illegitimately. This critical flaw in the authorization mechanism permits bypassing proper authentication checks to issue or obtain digital certificates, potentially enabling man-in-the-middle attacks, impersonation, or trust chain compromise.

MitigationUpgrade Atos Eviden IDRA to version 2.6.1 or later to obtain the vendor patch that remediates the access control vulnerability. After patching, audit all recently issued certificates for signs of unauthorized issuance.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Identify installed IDRA version
    Locate the IDRA installation directory and check the version information file or use the product's version command-line tool (e.g., idra --version or check the about panel in the admin console). Compare the reported version number against 2.6.1.
    Affected if The installed version is lower than 2.6.1 (e.g., 2.6.0, 2.5.x, or earlier).
  2. Confirm CA signing module is active
    Check the IDRA configuration to determine if the Certificate Authority signing functionality is enabled. Look for CA-related modules, profiles, or features in the admin interface or configuration files.
    Affected if The CA signing module is enabled and operational in the current installation.
  3. Review certificate issuance logs
    Examine IDRA certificate issuance logs for any certificates issued around the timeframe of the vulnerability disclosure or recently. Look for certificates with unexpected subject fields, issuer identities, or issuance times that do not match authorized operations.
    Affected if Certificates exist that were issued without corresponding authorized requests in the audit trail, or the logs show issuance activity from unexpected sources.
  4. Inspect access control audit records
    Review IDRA authentication and authorization audit logs for any failed access control checks, especially those related to CA signing operations. Look for patterns where authentication was bypassed or insufficient authorization checks occurred.
    Affected if Audit records show access attempts to CA signing functions that succeeded despite missing or invalid credentials.

You are affected if your IDRA version is below 2.6.1 and the CA signing module is enabled, particularly if certificate issuance logs show unexpected activity or access control logs indicate bypass attempts.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Atos Eviden IDRA to version 2.6.1 or later to obtain the vendor patch that remediates the access control vulnerability. After patching, audit all recently issued certificates for signs of unauthorized issuance.

Recommended fix Moderate confidence

2.6.1

  1. Identify the current version of Atos Eviden IDRA installed in your environment
  2. Upgrade Atos Eviden IDRA to version 2.6.1 or later to remediate the improper access control vulnerability
  3. Verify the upgrade was successful and the new version is running
  4. Confirm that CA signing operations now require proper authentication and authorization as expected

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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