dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-12564

MEDIUM · 6.9 CVSS v4.0 Published 2024-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Exposure of Sensitive Information to an Unauthorized Actor vulnerability was discovered in Open Design Alliance CDE inWEB SDK before 2025.3. Installing CDE Server with default settings allows unauthorized users to visit prometheus metrics page. This can allow attackers to understand more things about the target application which may help in further investigation and exploitation.

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

Open Design Alliance CDE inWEB SDK versions before 2025.3 expose the Prometheus metrics endpoint without authentication when installed with default settings. This allows unauthenticated attackers to access internal application metrics, potentially revealing sensitive information about system architecture, performance data, and internal operations that could aid further exploitation.

MitigationRestrict access to the Prometheus metrics endpoint by enabling authentication, implementing IP-based access controls, or disabling the metrics endpoint entirely if not required in production environments. Update to version 2025.3 or later which addresses this 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
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Open Design Alliance CDE inWEB SDK installation
    Locate the inWEB SDK installation directory and check for version information in product metadata, about dialog, or version file. Common locations include program files directories or application-specific installation folders.
    Affected if The installed version is present and is earlier than version 2025.3
  2. Verify Prometheus metrics endpoint exposure
    Attempt to access the Prometheus metrics endpoint on the application. The typical endpoint path is /metrics or /api/metrics, but check application documentation for the specific path. Use a web browser or curl command from a system that can reach the application server.
    Affected if The metrics endpoint returns HTTP 200 with Prometheus-formatted metric data without prompting for credentials
  3. Confirm default configuration is in use
    Examine the application configuration files for the metrics endpoint settings. Look for configuration parameters that control endpoint exposure and authentication. Check if the installation retains default settings versus having been hardened.
    Affected if The configuration shows default settings are active and authentication is not explicitly enabled for the metrics endpoint
  4. Test unauthenticated access
    Send a request to the metrics endpoint from an unauthorized network location or using a non-privileged account to determine if authentication is enforced.
    Affected if Metrics data is returned without requiring any authentication credentials

The environment is affected if Open Design Alliance CDE inWEB SDK version earlier than 2025.3 is installed with default settings, and the Prometheus metrics endpoint is accessible without 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

Restrict access to the Prometheus metrics endpoint by enabling authentication, implementing IP-based access controls, or disabling the metrics endpoint entirely if not required in production environments. Update to version 2025.3 or later which addresses this vulnerability.

Recommended fix Moderate confidence

2025.3

  1. Back up the current CDE Server installation and configuration data
  2. Download the fixed version of Open Design Alliance CDE inWEB SDK version 2025.3 from the official source (www.opendesign.com)
  3. Install or update the CDE Server to version 2025.3 following the standard installation procedures
  4. After upgrading, verify that the prometheus metrics page is no longer accessible to unauthorized users by attempting to access it without authentication
  5. Confirm the vulnerability is resolved by reviewing the application's security settings in version 2025.3

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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