dbcve.org
Eviden Cardos ApiApplication · Atos

CVE-2023-41099

HIGH · 7.8 CVSS v3.1 Published 2024-03-22
Fix available
A fix is available. Upgrade to 5.5.5.2811 or later.
See remediation →
80/100
Remediation priority · High
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
In the Windows installer in Atos Eviden CardOS API before 5.5.5.2811, Local Privilege Escalation can occur.(from a regular user to SYSTEM).

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

A local privilege escalation vulnerability exists in the Windows installer for Atos Eviden CardOS API versions prior to 5.5.5.2811. The installer improperly handles permissions during installation, allowing an authenticated regular user to gain SYSTEM-level privileges by exploiting the installation process.

MitigationUpdate CardOS API to version 5.5.5.2811 or later. Verify the patch through the vendor's official distribution channels and confirm the installer runs with appropriate privilege separation.

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
Eviden Cardos ApiApplication
Affected:>= 5.0, < 5.5.5.2811

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Confirm CardOS API is installed
    Check Windows Programs and Features (appwiz.cpl) or use 'Get-WmiObject Win32_Product' or check for CardOS API installation directories
    Affected if CardOS API does not appear in installed programs - not affected if not installed
  2. Locate the installed version
    Check the program's version information in Programs and Features, or look for version details in the installation directory (commonly in Program Files or Program Files (x86) under an Atos/CardOS folder)
    Affected if Unable to determine version - further investigation needed
  3. Compare version against affected range
    The affected version range is >= 5.0 and < 5.5.5.2811. If your installed version is 5.5.5.2811 or later, you are not affected. If it is 5.0 through 5.5.5.2810 (exclusive), you are in the affected range
    Affected if Installed version is 5.0 or higher but lower than 5.5.5.2811 - environment is affected
  4. Check for recent installer usage (optional context)
    Review installation logs or audit recent software installations to determine if the vulnerable installer was used
    Affected if Vulnerable version was installed recently - confirms exposure to the privilege escalation vector

You are affected if Atos Eviden CardOS API versions 5.0 through 5.5.5.2810 are currently installed on the system, as these versions were shipped with the vulnerable Windows installer.

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

Update CardOS API to version 5.5.5.2811 or later. Verify the patch through the vendor's official distribution channels and confirm the installer runs with appropriate privilege separation.

Recommended fix High confidence

5.5.5.2811 or later

  1. Obtain the fixed version 5.5.5.2811 or later of Eviden CardOS API from the vendor's support portal (support.bull.com)
  2. Review the release notes and migration documentation for version 5.5.5.2811
  3. Back up all existing CardOS API configuration data and settings
  4. Uninstall the current vulnerable version of CardOS API from the Windows system
  5. Install the new fixed version (5.5.5.2811 or later) using the Windows installer with appropriate privileges
  6. Verify the installation completed successfully and confirm the installed version matches the fixed release
  7. Test that CardOS API functionality operates normally after the upgrade
  8. Confirm that the Local Privilege Escalation vulnerability is no longer present by verifying installer permissions are properly restricted

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

Fix this in Eviden Cardos Api Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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