cve.bz

CVE-2023-49284 fishshell fish: Interpretation Conflict

6.6 mediumExploit referenceEPSS 0.5%Fix available

Medium (6.6) in fishshell fish. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
fish is a smart and user-friendly command line shell for macOS, Linux, and the rest of the family. fish shell uses certain Unicode non-characters internally for marking wildcards and expansions. It will incorrectly allow these markers to be read on command substitution output, rather than transforming them into a safe internal representation. While this may cause unexpected behavior with direct input (for example, echo \UFDD2HOME has the same output as echo $HOME), this may become a minor security problem if the output is being fed from an external program into a command substitution where this output may not be expected. This design flaw was introduced in very early versions of fish, predating the version control system, and is thought to be present in every version of fish released in the last 15 years or more, although with different characters. Code execution does not appear to be possible, but denial of service (through large brace expansion) or information disclosure (such as variable expansion) is potentially possible under certain circumstances. fish shell 3.6.2 has been released to correct this issue. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Severity

CVSS 3.1

6.6 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 42nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-436 Interpretation Conflict
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-49284 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-49284?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-49284?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-49284 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
fishshell:fishbefore 3.6.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12fish3.6.0-3.1+deb12u1DEBIAN-CVE-2023-49284
Debian13, 14fish3.6.4-1DEBIAN-CVE-2023-49284
Ubuntu16.04:LTS, 18.04:LTS, 24.04:LTS and 5 morefishno fix listedUBUNTU-CVE-2023-49284
SUSEPackage Hub 15 SP4fish3.3.1-bp154.3.3.1openSUSE-SU-2023:0404-1
SUSEPackage Hub 15 SP5fish3.3.1-bp155.4.3.1openSUSE-SU-2023:0405-1
openSUSELeap 15.4fish3.3.1-bp154.3.3.1openSUSE-SU-2023:0404-1
openSUSELeap 15.5fish3.3.1-bp155.4.3.1openSUSE-SU-2023:0405-1
openSUSETumbleweedfish3.6.4-1.1openSUSE-SU-2024:13501-1
Azure Linux2fish3.6.2-1AZL-32081

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

Attack patterns (CAPEC)

  • CAPEC-34 HTTP Response Splitting Likelihood: Medium · Severity: High
  • CAPEC-105 HTTP Request Splitting Likelihood: Medium · Severity: High
  • CAPEC-273 HTTP Response Smuggling Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON