dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-20624

MEDIUM · 5.7 CVSS v3.1 Published 2025-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
Exposure of sensitive information to an unauthorized actor for some Edge Orchestrator software for Intel(R) Tiber™ Edge Platform may allow an authenticated user to potentially enable information disclosure 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 · moderate confidence

This vulnerability in Intel(R) Tiber Edge Platform's Edge Orchestrator software allows an authenticated user to expose sensitive information to unauthorized parties through adjacent network access. The flaw enables information disclosure with adjacent attack vector and low privileges required, resulting in a Medium severity rating (CVSS 5.7).

MitigationContact Intel for the specific patch and review Edge Orchestrator access controls and network segmentation to limit adjacent attack surface until the update can be applied.

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

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/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. Confirm Intel Tiber Edge Platform and Edge Orchestrator are installed
    Locate and identify the Intel Tiber Edge Platform components on the system, specifically the Edge Orchestrator software component. Check installed programs or software inventory for 'Intel Tiber Edge Platform' or 'Edge Orchestrator'.
    Affected if The system has Intel Tiber Edge Platform with Edge Orchestrator software installed.
  2. Identify the Edge Orchestrator version
    Query the installed software version of Edge Orchestrator through system inventory tools, software management console, or command-line utilities that list installed packages. Compare the version number against any official Intel version documentation or release notes.
    Affected if The installed Edge Orchestrator version is any version prior to the Intel-provided patch.
  3. Verify adjacent network accessibility
    Check network configuration and firewall rules to determine if the Edge Orchestrator management interface or API is accessible from adjacent network segments (different subnet but same physical or logical network). Review network bindings and listening services.
    Affected if The Edge Orchestrator service is bound to interfaces accessible from adjacent network segments without proper network isolation.
  4. Review user authentication and authorization settings
    Examine Edge Orchestrator user accounts, roles, and access control configurations. Identify what low-privilege authenticated users can access and whether they can retrieve sensitive information through the software interface.
    Affected if Low-privilege authenticated users exist and have permissions that could allow retrieval of sensitive system information.
  5. Inspect network traffic and access logs
    Review Edge Orchestrator access logs and network traffic for any unusual queries or data access patterns from adjacent network sources, particularly by low-privilege users accessing sensitive data.
    Affected if Logs show low-privilege users successfully accessing sensitive information from adjacent network sources.

A user is affected if their environment runs Intel Tiber Edge Platform Edge Orchestrator software with any version prior to the Intel patch and has adjacent network accessibility combined with low-privilegle user accounts able to access sensitive information.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Contact Intel for the specific patch and review Edge Orchestrator access controls and network segmentation to limit adjacent attack surface until the update can be applied.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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