LiveActive security incident?Get immediate response
CVE Record

CVE-2022-41138: In Zutty before 0.13, DECRQSS in text written to the terminal can achieve arbitrary code execution.

In Zutty before 0.13, DECRQSS in text written to the terminal can achieve arbitrary code execution.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Zutty terminal emulator versions before 0.13 can be made to execute arbitrary code when hostile text is written to the terminal. This can turn viewing terminal output into a system compromise risk. The issue is rated critical, but the provided sources do not show active exploitation.

Executive priority

Prioritize remediation where Zutty is installed on administrator workstations, developer systems, or servers that display untrusted output. The business urgency is high because the stated impact is arbitrary code execution, even though active exploitation is not evidenced here.

Technical view

CVE-2022-41138 is a CWE-94 code injection flaw involving DECRQSS handling in Zutty before 0.13. The CVSS 3.1 score is 9.8, with high confidentiality, integrity, and availability impact. Primary references are the 0.13 comparison, upstream commit, Gentoo bug, and GLSA advisory.

Likely exposure

Exposure is likely limited to systems with Zutty installed at versions earlier than 0.13. The CVE metadata lacks CPEs and names affected vendor/product as n/a, so confirm through package and binary inventories.

Exploitation context

The source bundle reports arbitrary code execution through terminal text handling. It does not include exploit code, public exploitation evidence, or CISA KEV listing. Treat exploit status as unconfirmed from these sources.

Researcher notes

The core evidence is concise: Zutty before 0.13, DECRQSS handling, arbitrary code execution, CWE-94, and CVSS 9.8. Product metadata is incomplete, so validation should rely on actual installed package versions and the upstream 0.13 fix references.

Mitigation direction

  • Upgrade Zutty to version 0.13 or later.
  • Apply Gentoo guidance from GLSA-202209-25 where applicable.
  • Remove or disable vulnerable Zutty installations if upgrade is not immediately possible.
  • Review upstream and distribution advisories for environment-specific package names.
  • Limit rendering of untrusted terminal output until remediation is complete.

Validation and detection

  • Inventory endpoints and servers for Zutty installations.
  • Confirm installed Zutty versions are 0.13 or later.
  • Check Gentoo systems for GLSA-202209-25 remediation status.
  • Review software inventories for manually installed Zutty binaries.
  • Document any vulnerable hosts that require compensating controls.
Prepared
Confidence
medium
Sources
6

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-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process 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

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. 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-2022-41138 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

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
5Source 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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-41138Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.