dbcve.org
Factorytalk Policy ManagerApplication · Rockwellautomation

CVE-2024-6326

MEDIUM · 5.5 CVSS v3.1 Published 2024-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
An exposure of sensitive information vulnerability exists in the Rockwell Automation FactoryTalk® System Service. A malicious user could exploit this vulnerability by starting a back-up or restore process, which temporarily exposes private keys, passwords, pre-shared keys, and database folders when they are temporarily copied to an interim folder. This vulnerability is due to the lack of explicit permissions set on the backup folder. If private keys are obtained by a malicious user, they could impersonate resources on the secured network.

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

The FactoryTalk System Service backup/restore process copies sensitive materials (private keys, passwords, pre-shared keys, database folders) to a temporary interim folder without setting explicit access permissions. This allows any local user to read these sensitive files during the backup operation. If private keys are obtained, attackers could impersonate resources on the secured network.

MitigationConfigure the backup process to set restrictive explicit permissions (e.g., SYSTEM/Administrator only) on the interim folder before copying sensitive files, or use protected memory/encrypted temporary storage instead of plaintext file copies.

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 Policy ManagerApplication
Affected:= 6.40.0
Factorytalk System ServicesApplication
Affected:= 6.40.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed version of FactoryTalk Policy Manager
    Check the installed version of FactoryTalk Policy Manager on the system (typically via Add/Remove Programs, the application itself, or product documentation for version detection commands)
    Affected if The installed version is exactly 6.40.0
  2. Identify installed version of FactoryTalk System Services
    Check the installed version of FactoryTalk System Services on the system (typically via Add/Remove Programs, the application itself, or product documentation for version detection commands)
    Affected if The installed version is exactly 6.40.0
  3. Observe backup process temporary folder permissions
    When a backup operation is in progress, identify the temporary interim folder used by the FactoryTalk System Service and inspect its access permissions (check who has read access to the folder and its contents)
    Affected if Non-privileged local users have read access to the temporary folder containing sensitive backup materials
  4. Verify sensitive files are exposed during backup
    During a backup or restore operation, attempt to access or enumerate the temporary folder used by the backup process from a non-administrator account context
    Affected if A standard user account can read private keys, passwords, pre-shared keys, or database folders that should be restricted to SYSTEM or Administrator only

You are affected if you are running version 6.40.0 of either product AND your system allows non-privileged users to read sensitive files (private keys, passwords, PSKs, databases) from the temporary folder during FactoryTalk backup or restore operations.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure the backup process to set restrictive explicit permissions (e.g., SYSTEM/Administrator only) on the interim folder before copying sensitive files, or use protected memory/encrypted temporary storage instead of plaintext file copies.

Fix this in Factorytalk Policy Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2024-6326 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