CVE-2025-9364
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 · uneditedAn open database issue exists in the affected product and version. The security issue stems from an over permissive Redis instance. This could result in an attacker on the intranet accessing sensitive data and potential alteration of data.
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 confidenceThe vulnerability stems from an improperly secured Redis instance that lacks adequate access controls, allowing unauthorized network access from the intranet. An attacker could connect to the Redis service without authentication and read sensitive data or modify stored data.
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= 3.00.00= 3.01.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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 Factorytalk Analytics Logixai versionCheck the installed version of Factorytalk Analytics Logixai through the product's about or version information panel, or query the Windows registry at HKLM\SOFTWARE\Rockwell Software\FactoryTalk Analytics LogixAI if installed on WindowsAffected if Version equals 3.00.00 or 3.01.00
-
Locate the Redis configuration fileFind the redis.conf file in the product installation directory, typically under the Factorytalk Analytics Logixai or Redis subfolder in Program FilesAffected if The redis.conf file exists in the product directory and has not been modified from defaults
-
Verify Redis authentication is enabledOpen the redis.conf file and search for the 'requirepass' directiveAffected if The 'requirepass' directive is either missing, commented out, or set to an empty value meaning no password is required to connect
-
Check Redis network binding configurationInspect the 'bind' directive in redis.conf to see which network interfaces Redis is listening onAffected if Redis is bound to 0.0.0.0 or an IP address accessible from the intranet rather than localhost or a trusted internal interface only
-
Test Redis connectivity without authenticationUse redis-cli to attempt a connection to the Redis port (default 6379) from a remote or non-privileged context without providing credentials: redis-cli -h <target_ip> pingAffected if Redis responds with PONG without requiring authentication, indicating the instance is accessible without credentials
The environment is affected if Factorytalk Analytics Logixai version 3.00.00 or 3.01.00 is installed and the bundled Redis instance accepts connections without authentication or is exposed to untrusted network paths.
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 dataRemediate by enabling Redis authentication (requirepass), configuring appropriate ACLs, and restricting network binding to only trusted internal interfaces or networks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9364 — 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-2025-9364 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