Exacqvision Web ServiceApplication · Johnsoncontrols

CVE-2021-27664

CRITICAL · 9.8 CVSS v3.1 Published 2021-10-11
Fix available
A fix is available. Upgrade to after 20.06.11.0 or later.
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
Under certain configurations an unauthenticated remote user could be given access to credentials stored in the exacqVision Server.

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

In certain configurations, exacqVision Server allows unauthenticated remote attackers to access stored credentials, likely due to an authentication bypass or improper access control on credential storage mechanisms.

MitigationIdentify and remediate the vulnerable configuration settings; restrict network exposure of the exacqVision Server and review credential storage mechanisms to ensure proper authentication is enforced.

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
Exacqvision Web ServiceApplication
Affected:<= 20.06.11.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Confirm exacqVision Web Service is installed
    Check for exacqVision server software on the system by searching for the application process or service name, typically running as a Windows service or Linux daemon related to exacqVision
    Affected if The exacqVision server software is present on the system
  2. Determine the installed version
    Locate the exacqVision Web Service executable or version information, commonly found in the program's directory, About section, or Windows Programs and Features entry, and compare it to the affected version 20.06.11.0
    Affected if The installed version is 20.06.11.0 or lower
  3. Verify network exposure of the web service
    Determine if the exacqVision web interface (typically ports 80/443 or 8081/8082) is accessible from untrusted network locations or the internet without requiring authentication
    Affected if The web service port is exposed to untrusted networks without proper firewall restrictions or authentication barriers
  4. Test for unauthenticated credential access
    Attempt to access credential storage endpoints or configuration areas of the exacqVision web interface without providing valid login credentials to confirm if authentication is enforced
    Affected if Credential storage mechanisms or sensitive configuration pages are accessible without authentication
  5. Review credential storage configuration
    Examine the exacqVision configuration files or database where credentials are stored to verify that proper access controls and authentication requirements are in place
    Affected if Credential storage lacks proper authentication enforcement or access controls

You are affected if exacqVision Web Service version 20.06.11.0 or lower is installed and the credential storage is accessible without authentication due to improper access controls.

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 a release after 20.06.11.0
Interim mitigation

Identify and remediate the vulnerable configuration settings; restrict network exposure of the exacqVision Server and review credential storage mechanisms to ensure proper authentication is enforced.

Fix this in Exacqvision Web Service Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-27664 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2021-27664 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