CVE-2021-27474
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 · uneditedRockwell Automation FactoryTalk AssetCentre v10.00 and earlier does not properly restrict all functions relating to IIS remoting services. This vulnerability may allow a remote, unauthenticated attacker to modify sensitive data 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 · moderate confidenceFactoryTalk AssetCentre contains an access control vulnerability in its IIS remoting services where the web application fails to properly enforce authentication and authorization checks on certain functions. This allows remote, unauthenticated attackers to通过网络 access the IIS remoting endpoints and modify sensitive data within the FactoryTalk AssetCentre 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm FactoryTalk AssetCentre installationCheck for FactoryTalk AssetCentre installation by looking for the application in Windows Programs and Features, or searching for the installation directory (typically under C:\Program Files\Rockwell Software\FactoryTalk AssetCentre or similar paths). Also verify the FactoryTalk AssetCentre Windows service exists.Affected if FactoryTalk AssetCentre is not installed on the system
-
Identify installed versionLocate the version information in the installed application's About or Help section, or check the version in the installation directory's executable or manifest files. Compare the installed version number to the affected range (version 10.00 and earlier).Affected if Installed version is 10.00 or lower
-
Verify IIS is hosting FactoryTalk AssetCentreOpen IIS Manager (inetmgr) and check if FactoryTalk AssetCentre web application is deployed under the Default Web Site or a configured site. Look for an application pool associated with FactoryTalk AssetCentre.Affected if FactoryTalk AssetCentre web application is present in IIS
-
Check IIS remoting service exposureIn IIS Manager, examine the bindings and configuration of the FactoryTalk AssetCentre site. Check which ports and protocols (HTTP/HTTPS) are enabled. Review the web.config for exposed remoting endpoints (.rem or .soap extensions).Affected if IIS remoting endpoints are accessible over the network without restrictions
-
Inspect authentication settings on remoting endpointsIn IIS Manager, select the FactoryTalk AssetCentre application and view Authentication settings. Verify whether Anonymous Authentication is enabled or if Windows Authentication/Forms Authentication is properly required for all endpoints including remoting services.Affected if Anonymous authentication is enabled or authentication is not enforced on remoting endpoints
A system is affected if FactoryTalk AssetCentre version 10.00 or lower is installed with IIS remoting services exposed and lacking proper authentication enforcement.
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.
From vendor dataRestrict access to IIS remoting services by implementing proper authentication and authorization controls, network segmentation, and consider upgrading to a patched version if available. Apply principle of least privilege to all IIS remoting service functions.
- 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-27474 — 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-27474 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