Factorytalk AssetcentreApplication · Rockwellautomation

CVE-2021-27472

CRITICAL · 9.8 CVSS v3.1 Published 2022-03-23
Fix available
A fix is available. Upgrade to after 10.00 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
A vulnerability exists in the RunSearch function of SearchService service in Rockwell Automation FactoryTalk AssetCentre v10.00 and earlier, which may allow for the execution of remote unauthenticated arbitrary SQL statements.

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

A critical SQL injection vulnerability exists in the RunSearch function of the SearchService in Rockwell Automation FactoryTalk AssetCentre v10.00 and earlier. The flaw allows remote unauthenticated attackers to execute arbitrary SQL statements, likely due to improper input sanitization in the search query handling.

MitigationApply the vendor patch when available; in the interim, restrict network access to the SearchService port and monitor for suspicious SQL patterns in search queries.

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
Factorytalk AssetcentreApplication
Affected:<= 10.00

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 FactoryTalk AssetCentre installation
    Check for the presence of FactoryTalk AssetCentre software on the system. Look for the product in Windows Add/Remove Programs, or check for the installation directory under Program Files/Rockwell Software/FactoryTalk AssetCentre.
    Affected if FactoryTalk AssetCentre is installed on the system
  2. Check installed version number
    Open the Windows Control Panel and view the installed version of FactoryTalk AssetCentre in Programs and Features, or check the version information in the software's About/Help section.
    Affected if The installed version is 10.00 or earlier (any version up to and including 10.00)
  3. Identify if SearchService is running and exposed
    Check Windows Services for the SearchService related to FactoryTalk AssetCentre. Use netstat or a port scanner to determine if the SearchService port is listening on network interfaces accessible from outside.
    Affected if SearchService is running and bound to a network-accessible IP address (not localhost only)
  4. Verify SearchService is accessible without authentication
    Attempt to access the SearchService endpoint from a remote system or check configuration files for the service to determine if authentication is required for the RunSearch function.
    Affected if The RunSearch function does not require authentication or lacks proper input validation controls

The environment is affected if FactoryTalk AssetCentre version 10.00 or earlier is installed and the SearchService is network-accessible without proper authentication controls on the RunSearch function.

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 10.00
Interim mitigation

Apply the vendor patch when available; in the interim, restrict network access to the SearchService port and monitor for suspicious SQL patterns in search queries.

Fix this in Factorytalk Assetcentre Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
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,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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