dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2024-39328

MEDIUM · 6.8 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 →
74/100
Remediation priority · Elevated
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
Insecure Permissions in Atos Eviden IDRA and IDCA before 2.7.0. A highly trusted role (Config Admin) could exceed their configuration privileges in a multi-partition environment and access some confidential data. Data integrity and availability is not at risk.

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 · moderate confidence

The vulnerability allows a highly trusted Config Admin role to exceed their configuration privileges in a multi-partition environment and access confidential data outside their intended partition scope. This is an authorization bypass where partition-based access controls fail to properly restrict the Config Admin role to only their assigned partition.

MitigationUpgrade to version 2.7.0 or later and conduct verification testing to confirm partition-based access controls properly restrict Config Admin role access to only authorized partitions.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/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 multi-partition environment usage
    Review system configuration or documentation to confirm if the environment uses multiple partitions or tenants with isolated data scopes
    Affected if Multi-partition or multi-tenant architecture is deployed and the system relies on partition-based access controls
  2. Verify Config Admin role configuration
    Check system role management to confirm the Config Admin role exists and is assigned to users in the environment
    Affected if Config Admin role is actively configured and in use
  3. Compare installed version to fixed release
    Query the installed product version through system information, about dialog, or version command; compare against 2.7.0 as the fixed version
    Affected if Installed version is below 2.7.0
  4. Inspect partition-based access control rules
    Review access control or partition configuration settings to verify how Config Admin role permissions are scoped to specific partitions
    Affected if Partition-based access controls are defined but may allow Config Admin to access partitions outside their assigned scope

A user is affected if they operate a multi-partition environment with an installed version below 2.7.0 where the Config Admin role can potentially access data outside their assigned partition scope.

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 to version 2.7.0 or later and conduct verification testing to confirm partition-based access controls properly restrict Config Admin role access to only authorized partitions.

Recommended fix Moderate confidence

2.7.0 or later

  1. 1. Identify the current version of Atos Eviden IDRA and/or IDCA installed in your environment
  2. 2. Review the product documentation for upgrade prerequisites and compatibility requirements
  3. 3. Create a full backup of the current configuration and data
  4. 4. Test the upgrade in a non-production environment before deploying to production
  5. 5. Upgrade to version 2.7.0 or later following the vendor's documented upgrade procedure
  6. 6. Verify that the upgrade completed successfully and the service is operational
  7. 7. Confirm that the Config Admin role permissions are now properly restricted in multi-partition environments
Caveat Review vendor release notes for 2.7.0 for any configuration or behavioral changes that may affect existing setups

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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