dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-24840

MEDIUM · 5.8 CVSS v3.1 Published 2025-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/100
Remediation priority · Elevated
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
Improper access control for some Edge Orchestrator software before version 24.11.1 for Intel(R) Tiber(TM) Edge Platform may allow an unauthenticated user to potentially enable escalation of privilege via adjacent access.

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

Improper access control in Edge Orchestrator software for Intel Tiber Edge Platform before version 24.11.1 allows an unauthenticated attacker with adjacent network access to potentially escalate privileges.

MitigationUpgrade Edge Orchestrator software to version 24.11.1 or later to remediate the improper access control vulnerability.

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

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L

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 Intel Tiber Edge Platform installation
    Locate Edge Orchestrator software installation on the system by checking standard software directories, program files, or using system inventory tools to find Intel Tiber Edge related packages
    Affected if Edge Orchestrator software is present on the system before version 24.11.1
  2. Determine Edge Orchestrator version
    Use system package management tools, software inventory commands, or check the software's built-in version information to identify the exact installed version
    Affected if Installed version is lower than 24.11.1 (e.g., 24.x.x versions below 24.11.1 or any earlier major version)
  3. Assess network exposure
    Review firewall rules, network configuration, and access controls to determine if the Edge Orchestrator service is accessible from adjacent network segments
    Affected if The service is exposed to adjacent network segments without proper network segmentation or access restrictions
  4. Verify authentication configuration
    Check Edge Orchestrator configuration files and settings for authentication enforcement and access control policies
    Affected if Authentication is not properly enforced or access controls are misconfigured, allowing unauthenticated access

A system is affected if Intel Tiber Edge Platform with Edge Orchestrator software version below 24.11.1 is installed and accessible from adjacent network segments without proper authentication controls in place.

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 Edge Orchestrator software to version 24.11.1 or later to remediate the improper access control vulnerability.

Recommended fix Moderate confidence

24.11.1

  1. 1. Identify the current version of Intel(R) Tiber(TM) Edge Platform Edge Orchestrator software installed in the environment
  2. 2. If the current version is earlier than 24.11.1, obtain the version 24.11.1 update from Intel's official support channels or download portal
  3. 3. Review Intel's upgrade documentation for Edge Orchestrator software
  4. 4. Apply the version 24.11.1 update following the documented upgrade procedure
  5. 5. After upgrading, verify that the Edge Orchestrator service is running correctly
  6. 6. Confirm the installed version is 24.11.1 or later

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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