FlexloggerApplication · Ni

CVE-2024-6121

HIGH · 7.8 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to after 2024 or later.
See remediation →
80/100
Remediation priority · High
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 out-of-date version of Redis shipped with NI SystemLink Server is susceptible to multiple vulnerabilities, including CVE-2022-24834. This affects NI SystemLink Server 2024 Q1 and prior versions. It also affects NI FlexLogger 2023 Q2 and prior versions which installed this shared service.

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

NI SystemLink Server and NI FlexLogger ship with an outdated version of Redis that is vulnerable to CVE-2022-24834 and potentially other Redis vulnerabilities. This is a supply chain vulnerability where the bundled third-party component contains known security flaws.

MitigationUpdate NI SystemLink Server to a version newer than 2024 Q1 and NI FlexLogger to a version newer than 2023 Q2, or apply any available NI patches that update the bundled Redis component to a patched version.

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
FlexloggerApplication
Affected:<= 2023= 2023
SystemlinkApplication
Affected:<= 2024= 2024

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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Check if NI FlexLogger is installed
    Open Windows Control Panel > Programs and Features, or check the installation directory (typically C:\Program Files\National Instruments\FlexLogger) for the presence of FlexLogger. Note the installed version from the program listing.
    Affected if FlexLogger version is 2023 or earlier (2023, 2022, 2021, etc.)
  2. Check if NI SystemLink Server is installed
    Open Windows Control Panel > Programs and Features, or check the installation directory (typically C:\Program Files\National Instruments\SystemLink Server) for the presence of SystemLink Server. Note the installed version from the program listing.
    Affected if SystemLink Server version is 2024 or earlier (2024, 2023, 2022, etc.)
  3. Identify the bundled Redis component
    Look for a Redis installation within the NI product directories. Common paths include C:\Program Files\National Instruments\FlexLogger\redis or C:\Program Files\National Instruments\SystemLink Server\redis. Check for redis-server.exe or redis-cli.exe files.
    Affected if Redis executable files exist within the NI product installation folders, indicating the product bundles Redis.
  4. Determine if the bundled Redis service is running
    Open Windows Services (services.msc) and look for a Redis service, or run 'sc query redis' or 'Get-Service redis' in PowerShell to check service status.
    Affected if A Redis service associated with NI products is currently running, making the vulnerability potentially exploitable.

You are affected if you have NI FlexLogger 2023 or earlier, or NI SystemLink Server 2024 or earlier, and the bundled Redis component is present and running.

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
Upgrade available Upgrade to a release after 2024
Interim mitigation

Update NI SystemLink Server to a version newer than 2024 Q1 and NI FlexLogger to a version newer than 2023 Q2, or apply any available NI patches that update the bundled Redis component to a patched version.

Fix this in Flexlogger Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6121 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6121 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