CVE-2024-6122
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 incorrect permission in the installation directory for the shared NI SystemLink Server KeyValueDatabase service may result in information disclosure via local access. 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 confidenceThe NI SystemLink Server KeyValueDatabase service is installed with incorrect file system permissions in its installation directory, allowing local users to access sensitive data that should be restricted. This shared service is bundled with NI SystemLink Server 2024 Q1 and prior versions, as well as NI FlexLogger 2023 Q2 and prior versions.
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<= 2024= 2024<= 2023= 2023CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify if NI SystemLink Server or NI FlexLogger is installedCheck for the presence of the software in the system: look for 'National Instruments' or 'NI' in Programs and Features, or search for known installation directories such as 'C:\Program Files\National Instruments' or 'C:\ProgramData\National Instruments'Affected if Neither NI SystemLink Server nor NI FlexLogger is installed on the system - if not present, the vulnerability does not apply
-
Determine the installed version of NI SystemLink Server or NI FlexLoggerOpen Programs and Features, find the NI product entry, and note the version number shown (for SystemLink: 2024 Q1 or earlier; for FlexLogger: 2023 Q2 or earlier)Affected if The installed version is 2024 or prior for SystemLink, or 2023 or prior for FlexLogger - these versions are within the affected range
-
Locate the KeyValueDatabase service installation directorySearch the file system for a folder named 'KeyValueDatabase' or 'KVDB' within the NI installation paths, typically found under 'C:\Program Files\National Instruments\SystemLink\Server' or similar paths under the NI program directoryAffected if The KeyValueDatabase directory exists on the system - its presence indicates the vulnerable service component is installed
-
Inspect file system permissions on the KeyValueDatabase directoryRight-click the KeyValueDatabase folder, go to Properties > Security tab, and review the listed users and groups with access. Check if non-privileged users, 'Users' group, or 'Everyone' have Read, Write, or Modify permissions to this directoryAffected if Non-administrative accounts, the 'Users' group, or 'Everyone' are granted Read, Write, or Modify access to the KeyValueDatabase directory - overly permissive ACLs indicate the vulnerability is present
A user is affected if NI SystemLink Server 2024 or prior, or NI FlexLogger 2023 or prior is installed, the KeyValueDatabase service directory exists, and that directory grants access to non-privileged local users beyond what the service account requires.
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 vendor-supplied patches or hotfixes that correct the directory permissions on the KeyValueDatabase service installation. If no patch is available, manually review and restrict directory permissions to authorized service accounts only.
NI SystemLink Server 2024 Q2 or later; NI FlexLogger 2023 Q3 or later (if using shared SystemLink service)
- Identify the installed NI SystemLink Server or FlexLogger version via NI MAX or the Add/Remove Programs control panel
- For NI SystemLink Server: Upgrade to a version released after 2024 Q1 that includes the corrected directory permissions
- For NI FlexLogger: If the shared NI SystemLink Server KeyValueDatabase service was installed, upgrade to a version released after 2023 Q2 that includes the corrected directory permissions
- After upgrade, verify that the KeyValueDatabase service installation directory has restricted permissions (only SYSTEM, Administrators, and the service account should have access)
- Confirm the fix by reviewing the directory permissions on the KeyValueDatabase installation folder
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6122 — 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-2024-6122 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