zsh-static 5.4.2-3ubuntu3.1: zsh-static 5.4.2-3ubuntu3.1 for Ubuntu 18.04.6 LTS (bionic)

zsh-static 5.4.2-3ubuntu3.1, released September 4, 2018, fixes 3 CVEs in zsh-static. None of them is reported as exploited. Patch Radar priority: Routine. The product is no longer supported.

RoutineUnsupported product

CVEs closed

None rated Critical

Exploited

None reported

Highest CVSS

n/a

No CVSS score published

Highest EPSS

0.0272

86th percentile

Priority of the 3 CVEs

Patch now 0
                                Urgent 0
                                High 0
                                Routine 3

Fixed package versions

Product	Release	Fixed in
zsh-static	Ubuntu 18.04.6 LTS (bionic)	5.4.2-3ubuntu3.1

CVEs this fix closes

Priority	CVE	Title	CVSS	EPSS	Exploitation
Routine	CVE-2018-13259	zsh: An issue was discovered in zsh before 5.6	n/a	0.0272	None reported
Routine	CVE-2018-0502	zsh: An issue was discovered in zsh before 5.6	n/a	0.0249	None reported
Routine	CVE-2018-1100	zsh: zsh through version 5.4.2 is vulnerable to a stack-based buffer overflow in the utils.c:checkmailpath function	n/a	0.0053	None reported

Also fixes CVE-2018-13259

zsh 5.4.2-3ubuntu3.1
zsh on Ubuntu 18.04.6 LTS (bionic)
zsh-common 5.4.2-3ubuntu3.1
zsh-common on Ubuntu 18.04.6 LTS (bionic)

For tools and AI agents

This page as data: JSON · Markdown

Link to this page

If this page saved you time, a link to it in your ticket, advisory or write-up helps others find it.

HTML

<a href="https://patchblox.com/security/fix/linux/ubuntu-bionic-zsh-static-5.4.2-3ubuntu3.1">zsh-static 5.4.2-3ubuntu3.1 on Patchblox Patch Radar</a>

Reusing the data? How to credit Patch Radar.

Which servers are still behind?

Patchblox compares the installed package on every Linux machine against the fixed version for its release, including machines reported through Azure Update Manager.

Get a demo

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.