dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2024-42017

CRITICAL · 10.0 CVSS v3.1 Published 2024-09-30
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 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
An issue was discovered in Atos Eviden iCare 2.7.1 through 2.7.11. The application exposes a web interface locally. In the worst-case scenario, if the application is remotely accessible, it allows an attacker to execute arbitrary commands with system privilege on the endpoint hosting the application, without any authentication.

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 iCare versions 2.7.1-2.7.11 contains an unauthenticated remote code execution vulnerability where the locally-exposed web interface can be abused to execute arbitrary commands with SYSTEM privileges if the application is accessible over a network, requiring no authentication.

MitigationImmediately restrict network access to ensure the web interface is not remotely accessible. Apply vendor-supplied security patches once available and verify the fix in a non-production environment before deployment.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 the installed iCare version
    Locate the iCare application and check its version information, typically found in the application properties, about page, or installation directory
    Affected if The installed version is 2.7.1, 2.7.2, 2.7.3, 2.7.4, 2.7.5, 2.7.6, 2.7.7, 2.7.8, 2.7.9, 2.7.10, or 2.7.11
  2. Confirm the web interface is network-accessible
    Attempt to access the iCare web interface from a system other than the localhost, or inspect network binding configuration to determine if the service listens on non-loopback interfaces
    Affected if The web interface responds to requests from remote systems or binds to IP addresses other than 127.0.0.1/localhost
  3. Verify network exposure of the service
    Check network configuration, firewall rules, or service binding settings to determine if the iCare web service port is exposed to network segments beyond the local machine
    Affected if The service port is open to network traffic and not restricted to localhost or trusted internal networks
  4. Test web interface authentication requirement
    Attempt to access the iCare web interface without providing credentials to determine if authentication is enforced
    Affected if The web interface allows access without any authentication credentials
  5. Review network access controls
    Inspect any available access control lists, network filters, or web server configuration that may restrict access to the iCare interface
    Affected if There are no access restrictions preventing unauthenticated remote access to the web interface

You are affected if Atos Eviden iCare version 2.7.1 through 2.7.11 is installed and its web interface is accessible over the network without requiring authentication.

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

Immediately restrict network access to ensure the web interface is not remotely accessible. Apply vendor-supplied security patches once available and verify the fix in a non-production environment before deployment.

Recommended fix High confidence

Latest version beyond 2.7.11 (contact Atos Eviden support for exact fixed release)

  1. 1. Identify all systems running Atos Eviden iCare versions 2.7.1 through 2.7.11
  2. 2. Immediately restrict network access to the iCare web interface by placing it behind a firewall or VPN - do not expose it directly to the internet or untrusted networks
  3. 3. Upgrade iCare to the latest available version beyond 2.7.11 (check with Atos Eviden support for the specific fixed release)
  4. 4. After upgrading, verify that authentication is now required to access the web interface
  5. 5. Confirm that command execution now requires proper authorization credentials
Caveat Test upgrade in non-production environment first as minor version upgrades typically have low risk but always verify compatibility with your specific iCare configuration

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,140
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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