# CVE-2019-18276: Privilege escalation in n/a

> An attacker with shell access can regain privileges via runtime loading of a new builtin due to incorrect privilege dropping in Bash.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Nov 2019
- **Updated:** 14 Oct 2026
- **Also known as:** CLSA-2022-1650909007, CLSA-2022-1650910003, CLSA-2022-1651685129, CLSA-2025-1761326171, DEBIAN-CVE-2019-18276, GHSA-jcxc-5f87-vq5m, MGASA-2021-0288, RHSA-2021:1679, UBUNTU-CVE-2019-18276, USN-5380-1

## What is CVE-2019-18276?

CVE-2019-18276 is a high-severity vulnerability in Netapp Hci Management Node, published on 28 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in disable_priv_mode in shell.c in GNU Bash through 5.0 patch 11. By default, if Bash is run with its effective UID not equal to its real UID, it will drop privileges by setting its effective UID to its real UID. However, it does so incorrectly. On Linux and other systems that support "saved UID" functionality, the saved UID is not dropped. An attacker with command execution in the shell can use "enable -f" for runtime loading of a new builtin, which can be a shared object that calls setuid() and therefore regains privileges. However, binaries running with an effective UID of 0 are unaffected.

Weakness: CWE-273 (Improper Check for Dropped Privileges)

## Which versions are affected by CVE-2019-18276?

It affects 5 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bash` | Red Hat:enterprise_linux:8::baseos | All versions | 0:4.4.19-14.el8 |
| `bash-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:4.4.19-14.el8 |
| `bash-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:4.4.19-14.el8 |
| `bash-doc` | Red Hat:enterprise_linux:8::baseos | All versions | 0:4.4.19-14.el8 |

Products: Gnu Bash, Netapp Hci Management Node, Netapp Oncommand Unified Manager, Netapp Solidfire, Oracle Communications Cloud Native Core Policy.

## How do I fix CVE-2019-18276?

Apply the vendor's patch.

## Is CVE-2019-18276 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-18276 exists.

Public exploit code:

- https://github.com/M-ensimag/CVE-2019-18276 (github_poc): https://github.com/M-ensimag/CVE-2019-18276
- https://github.com/SABI-Ensimag/CVE-2019-18276 (github_poc): https://github.com/SABI-Ensimag/CVE-2019-18276

## Other vulnerabilities in Netapp Hci Management Node

- [CVE-2014-6278](https://insights.sbomify.com/CVE-2014-6278/): GNU Bash OS Command Injection (high 8.8, exploited in the wild)
- [CVE-2014-7186](https://insights.sbomify.com/CVE-2014-7186/): Memory corruption in n/a (critical 10.0)
- [CVE-2014-7187](https://insights.sbomify.com/CVE-2014-7187/): Memory corruption in n/a (critical 10.0)
- [CVE-2014-6277](https://insights.sbomify.com/CVE-2014-6277/): Code injection in n/a (critical 10.0)
- [CVE-2022-3715](https://insights.sbomify.com/CVE-2022-3715/): Memory corruption in bash (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18276 and fix it if it is affected.

What it is: CVE-2019-18276 is a high-severity vulnerability in Netapp Hci Management Node, published on 28 Nov 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-18276 exists.

Affected product: Netapp Hci Management Node. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-18276/ (Markdown: https://insights.sbomify.com/CVE-2019-18276/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-18276
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-18276
- OSV: https://osv.dev/vulnerability/CVE-2019-18276

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-18276/
Summaries are generated and may contain mistakes; the official description above is the record.