LiveActive security incident?Get immediate response
CVE Record

CVE-2021-42811: Vulnerability in SafeNet KeySecure

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in SafeNet KeySecure allows an authenticated user to read arbitrary files from the underlying system on which the product is deployed.

LowCVSS 3.3Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

SafeNet KeySecure 8.12.4 has a path traversal flaw that could let an authenticated user read files outside intended directories on the underlying system. The public record rates this low severity because it requires local/authenticated access and affects confidentiality only. For key management systems, treat exposure seriously where many users have access.

Executive priority

Handle through the normal vulnerability management cycle, but accelerate remediation for KeySecure systems with broad user access or sensitive local configuration. The issue is low CVSS, yet it affects a security product that may sit near sensitive key-management workflows.

Technical view

CVE-2021-42811 is a CWE-22 path traversal issue in Thales DIS SafeNet KeySecure 8.12.4. The CVSS 3.1 vector is 3.3, AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N. Sources describe arbitrary file read by an authenticated user, with no integrity or availability impact stated.

Likely exposure

Exposure is limited to organizations running SafeNet KeySecure 8.12.4 where authenticated users can interact with the affected component. Risk increases if access to the host or management environment is broadly granted, shared, or weakly monitored.

Exploitation context

The supplied sources do not indicate active exploitation, and the CVE is not listed as KEV. Exploitation requires privileges according to the CVSS vector and authenticated access according to the description. No public exploit details are included in the source bundle.

Researcher notes

The public bundle names the vulnerable product and version but does not provide affected endpoints, exploit procedure, fixed versions, or detailed mitigation text. Validation should stay inventory- and configuration-focused, then defer remediation specifics to Thales advisory KB0025953.

Mitigation direction

  • Identify any SafeNet KeySecure 8.12.4 deployments.
  • Review Thales KB0025953 for vendor-approved fixes or mitigations.
  • Restrict authenticated access to trusted KeySecure operators only.
  • Harden host access controls around KeySecure systems.
  • Monitor for unusual file access or application error patterns.

Validation and detection

  • Confirm installed SafeNet KeySecure versions against asset inventory.
  • Check whether any deployment is specifically version 8.12.4.
  • Review user roles with access to KeySecure or its host.
  • Validate current remediation status against Thales guidance.
  • Review logs for suspicious file-read failures or anomalies.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-42811 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3.3CVSS 3.1LowCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N1.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.3Low
CVSS 3.1 vector shape for CVE-2021-42811Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Thales DISSafeNet KeySecure8.12.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.