CVE-2016-9401: Use After Free

Published Nov 18, 2016
·
Updated

A vulnerability was found in popd. It can be tricked to free a user supplied address in the following way:

$ popd +-111111

This could be used to bypass restricted shells (rsh) on some environments to cause use-after-free.

References:

http://seclists.org/oss-sec/2016/q4/445

Other sources

popd in bash might allow local users to bypass the restricted shell and cause a use-after-free via a crafted address.

Affected Software

22 affected components
GNU Bash<4.4
GNU Bash=4.4-patch1
GNU Bash=4.4-patch2
GNU Bash=4.4-patch3
GNU Bash=4.4-patch4
GNU Bash=4.4-patch5
Debian Debian Linux=8.0
redhat Enterprise Linux Desktop=6.0
redhat Enterprise Linux Desktop=7.0
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Server=7.0
redhat Enterprise Linux Server Aus=7.4
redhat Enterprise Linux Server Aus=7.6
redhat Enterprise Linux Server Aus=7.7
redhat Enterprise Linux Server Eus=7.4
redhat Enterprise Linux Server Eus=7.5
redhat Enterprise Linux Server Eus=7.6
redhat Enterprise Linux Server Eus=7.7
redhat Enterprise Linux Server Tus=7.6
redhat Enterprise Linux Server Tus=7.7
redhat Enterprise Linux Workstation=6.0
redhat Enterprise Linux Workstation=7.0

Event History

Nov 18, 2016
Data Sourced
via Red Hat·08:52 AM
DescriptionSeverityAffected Software
Jan 23, 2017
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description
Data Sourced
via NVD·09:59 PM
DescriptionSeverityWeaknessAffected Software
Jul 6, 57568
Event
via NVD·01:16 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2016-9401?

CVE-2016-9401 is considered a moderate severity vulnerability because it can be exploited to cause a use-after-free condition.

2

How do I fix CVE-2016-9401?

To fix CVE-2016-9401, users should update to a patched version of GNU Bash that includes the security fix.

3

What types of systems are affected by CVE-2016-9401?

CVE-2016-9401 affects GNU Bash versions prior to 4.4 and specific patched versions of 4.4.

4

What are the potential impacts of CVE-2016-9401?

Exploitation of CVE-2016-9401 could allow an attacker to bypass restricted shells and execute unauthorized commands.

5

What versions of GNU Bash are safe from CVE-2016-9401?

Versions of GNU Bash that have been patched after 4.4 or any version higher than 4.4 are safe from CVE-2016-9401.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203