CVE-2021-27476
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 · uneditedA vulnerability exists in the SaveConfigFile function of the RACompare Service, which may allow for OS command injection. This vulnerability may allow a remote, unauthenticated attacker to execute arbitrary commands in Rockwell Automation FactoryTalk AssetCentre v10.00 and earlier.
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 confidenceA command injection vulnerability exists in the SaveConfigFile function of the RACompare Service in Rockwell Automation FactoryTalk AssetCentre v10.00 and earlier. A remote, unauthenticated attacker can inject and execute arbitrary OS commands due to insufficient input validation in the configuration file saving function.
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<= 10.00CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if FactoryTalk AssetCentre is installedLook for FactoryTalk AssetCentre installation directories (commonly under C:\Program Files\Rockwell Software\ or C:\Program Files (x86)\Rockwell Software\) or check Windows Programs and Features for 'FactoryTalk AssetCentre' entryAffected if FactoryTalk AssetCentre is not installed on the system
-
Determine the installed version of FactoryTalk AssetCentreCheck the program version in Windows Programs and Features, or look for version information in the installation directory (often in an About or version file)Affected if The installed version is 10.00 or earlier (any version up to and including 10.00)
-
Verify the RACompare Service exists and is runningOpen Windows Services and look for a service named 'RACompare' or similar, or check running processes for RACompare-related executablesAffected if The RACompare Service is present and running on the system
-
Check network exposure of the RACompare ServiceIdentify which ports the RACompare Service listens on (check service configuration or documentation for default port), then use netstat or port scanning to determine if those ports are accessible from untrusted networksAffected if The RACompare Service port is exposed to untrusted/network-accessible interfaces without proper network segmentation
The system is affected if FactoryTalk AssetCentre version 10.00 or earlier is installed with the RACompare Service running and accessible on the network.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the vendor patch or update FactoryTalk AssetCentre to a version beyond v10.00. If immediate patching is not possible, network segment the affected system and restrict access to the RACompare Service port.
FactoryTalk AssetCentre version 10.00 with latest security patches applied, or upgrade to the next major version if available from Rockwell Automation
- 1. Identify current FactoryTalk AssetCentre version through the Help > About section in the application or via the RACompare Service configuration.
- 2. Contact Rockwell Automation technical support or visit their official patch download portal to obtain the latest security update for FactoryTalk AssetCentre.
- 3. Download the patched version (version 10.00 or later updates/patches that address CVE-2021-27476).
- 4. Before applying the update, perform a complete backup of the FactoryTalk AssetCentre configuration and database.
- 5. Apply the security update following the installation instructions provided in the Rockwell Automation advisory.
- 6. Verify the RACompare Service is running correctly after the update.
- 7. Validate that the SaveConfigFile function no longer accepts unsanitized input that could lead to OS command injection.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27476 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-27476 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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