CVE-2021-27470
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 deserialization vulnerability exists in how the LogService.rem service in Rockwell Automation FactoryTalk AssetCentre v10.00 and earlier verifies serialized data. This vulnerability may allow a remote, unauthenticated attacker to execute arbitrary commands in FactoryTalk AssetCentre.
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 critical deserialization vulnerability exists in the LogService.rem component of Rockwell Automation FactoryTalk AssetCentre v10.00 and earlier. The service fails to properly validate serialized data before processing it, allowing unauthenticated remote attackers to inject malicious serialized payloads that result in arbitrary command execution on the affected system.
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.
-
Confirm FactoryTalk AssetCentre installationCheck for FactoryTalk AssetCentre in installed programs list (Windows Control Panel > Programs and Features) or look for its installation directory under Program Files/Rockwell SoftwareAffected if FactoryTalk AssetCentre is present on the system
-
Identify installed versionLocate the FactoryTalk AssetCentre installation directory and check version information in the application properties, or use the product's About/Version dialog if accessibleAffected if Version is 10.00 or earlier, or version cannot be determined but product is present
-
Verify LogService.rem component statusCheck if LogService (a Windows service related to FactoryTalk AssetCentre logging) is running by opening Services console (services.msc) and looking for LogService or similar FactoryTalk-related servicesAffected if LogService or FactoryTalk logging services are running and exposed
-
Assess network exposureUse netstat or a network port scanner to check for listening ports associated with FactoryTalk services (typically .NET remoting ports), and verify whether these ports are bound to 0.0.0.0 or accessible from untrusted networksAffected if The LogService.rem or FactoryTalk AssetCentre services are listening on accessible network interfaces and accept unauthenticated connections
A system is affected if FactoryTalk AssetCentre version 10.00 or earlier is installed with the LogService.rem component running and network-accessible to untrusted users.
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 for CVE-2021-27470 to FactoryTalk AssetCentre. If patching is not immediately possible, restrict network access to the LogService.rem and associated FactoryTalk services to prevent unauthenticated remote exploitation.
Latest available version of FactoryTalk AssetCentre beyond v10.00 (contact Rockwell Automation for specific version number)
- 1. Identify the current FactoryTalk AssetCentre version installed in the environment
- 2. Contact Rockwell Automation technical support or visit their support portal to obtain the latest patched version of FactoryTalk AssetCentre
- 3. Before upgrading, backup all critical data and configurations
- 4. Download the latest FactoryTalk AssetCentre version from Rockwell Automation's official download site or obtain via support
- 5. Follow Rockwell Automation's official upgrade documentation to install the patched version
- 6. After upgrading, verify that the LogService.rem service is functioning correctly
- 7. Test that FactoryTalk AssetCentre is operational and validate the vulnerability is no longer present
- 8. Monitor Rockwell Automation's security advisories for future updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2021-27470 — 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-27470 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