dbcve.org
BcproApplication · Johnsoncontrols

CVE-2018-10624

MEDIUM · 6.5 CVSS v3.0 Published 2018-08-01
Fix available
A fix is available. Upgrade to 3.0.2 or later.
See remediation →
70/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
In Johnson Controls Metasys System Versions 8.0 and prior and BCPro (BCM) all versions prior to 3.0.2, this vulnerability results from improper error handling in HTTP-based communications with the server, which could allow an attacker to obtain technical information.

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 is an information disclosure vulnerability in Johnson Controls Metasys System (v8.0 and prior) and BCPro (prior to v3.0.2) caused by improper error handling in HTTP-based server communications. The improper handling could cause the server to return detailed technical information in error responses that could aid further attacks.

MitigationImplement proper error handling that returns generic error messages to clients while logging detailed errors server-side. Update to patched versions of Metasys (v8.0+) and BCPro (v3.0.2+) when available.

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
BcproApplication
Affected:< 3.0.2
Metasys SystemApplication
Affected:<= 8.0

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

CVSS:3.0/AV:A/AC:L/PR:N/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. Identify installed Metasys System version
    Locate the Metasys installation directory or check the application version through the Metasys UI (typically found in About or System Information section). On Windows systems, check registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Johnson Controls\Metasys or look for version info in the installation folder.
    Affected if The installed version is 8.0 or any version prior to 8.0
  2. Identify installed BCPro version
    Locate the BCPro installation directory or check the application version through the BCPro UI. On Windows systems, check registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Johnson Controls\BCPro or look for version info in the installation folder.
    Affected if The installed version is prior to 3.0.2
  3. Verify HTTP error response content
    Send malformed or invalid HTTP requests to the Metasys or BCPro web server endpoints (typically ports 8080, 8443, or standard web ports). Examples: request non-existent pages, send malformed headers, or trigger authentication errors.
    Affected if Error responses contain detailed technical information such as stack traces, internal file paths, software version numbers, database connection strings, or system configuration details rather than generic error messages
  4. Check server configuration for custom error pages
    Examine the web server configuration files (IIS web.config, Tomcat server.xml, or application-specific config) for custom error handling settings. Look for <customErrors> in .NET configs or error-page directives in Java configs.
    Affected if Custom error pages are not configured or are set to display detailed error messages (mode=Off is not set for sensitive endpoints)
  5. Review application logs for exposed information
    Access the application logs directory (typically found in the installation folder under Logs or EventLogs). Search for error entries that contain sensitive system information being logged.
    Affected if Logs contain detailed stack traces, full exception messages with system paths, or version information that should not be exposed

You are affected if you are running Metasys System version 8.0 or prior, or BCPro version prior to 3.0.2, AND your HTTP error responses expose detailed technical information rather than generic messages.

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
Upgrade available Upgrade to 3.0.2 or later
Fixed in 3.0.2
Interim mitigation

Implement proper error handling that returns generic error messages to clients while logging detailed errors server-side. Update to patched versions of Metasys (v8.0+) and BCPro (v3.0.2+) when available.

Fix this in Bcpro Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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