LiveActive security incident?Get immediate response
CVE Record

CVE-2021-42702: Inkscape Access of Uninitialized Pointer

Inkscape version 0.91 can access an uninitialized pointer, which may allow an attacker to have access to unauthorized information.

LowCVSS 3.3Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a low-severity information-disclosure flaw in Inkscape 0.91. A user must interact locally with content that triggers an uninitialized pointer access. The published impact is limited to possible unauthorized information access, with no stated integrity or availability impact. Treat it as workstation hygiene, not a broad remote compromise signal.

Executive priority

Low priority unless Inkscape 0.91 is still used in sensitive desktop or industrial-support workflows. The business risk is limited information exposure requiring user interaction, but obsolete software should still be retired through normal endpoint hygiene processes.

Technical view

CVE-2021-42702 is CWE-824 in Inkscape 0.91. The CVSS 3.1 vector is AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N, indicating local attack conditions, low complexity, no privileges, required user interaction, and low confidentiality impact. The sources do not describe the exact trigger path or remediation version.

Likely exposure

Exposure is likely where Inkscape 0.91 is installed on user workstations or engineering systems. No server-side or network-exposed product is identified in the source bundle. Organizations using Inkscape only in later versions may not be affected, but version confirmation is required.

Exploitation context

The CVE is not listed in KEV, and the provided sources do not claim active exploitation. The CVSS vector requires local access conditions and user interaction. The public details are sparse, so avoid assuming weaponized exploitation or a specific malicious file workflow from this bundle alone.

Researcher notes

The source bundle identifies the affected product and CVSS properties but not the vulnerable code path, trigger conditions, proof-of-concept status, or fixed release. Analysis should therefore stay conservative: validate version exposure first, then use vendor or advisory updates for remediation specifics.

Mitigation direction

  • Inventory systems for Inkscape 0.91 installations.
  • Review Inkscape or vendor guidance for fixed or supported versions.
  • Prioritize removal or upgrade of unsupported 0.91 installations.
  • Limit use of untrusted graphic files on affected workstations.
  • Document exceptions for systems that cannot be updated immediately.

Validation and detection

  • Confirm installed Inkscape versions across endpoints and engineering images.
  • Check whether any business workflow depends on Inkscape 0.91.
  • Review vendor advisories for remediation details before closing findings.
  • Verify vulnerable versions are removed, upgraded, or risk-accepted.
  • Confirm no compensating controls rely on unsupported assumptions.
Prepared
Confidence
medium
Sources
4

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 · low confidence lookup

CWE-824: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
cve · low confidence lookup

CVE-2021-42702 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:N/UI:R/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
3Source 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:N/UI:R/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-42702Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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
InkscapeInkscape0.91Listed
Weakness

CWE details

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

CWE-824 · source CWE mapping

Access of Uninitialized Pointer

Access of Uninitialized Pointer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.