# CVE-2019-16396: Use after free in n/a

> A use-after-free vulnerability in GnuCOBOL allows attackers to execute arbitrary code or cause denial of service via crafted COBOL source code.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-16396, GHSA-gww5-4w7g-8gw6, UBUNTU-CVE-2019-16396

## What is CVE-2019-16396?

CVE-2019-16396 is a high-severity use after free vulnerability in n/a, published on 17 Sep 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

GnuCOBOL 2.2 has a use-after-free in the end_scope_of_program_name() function in cobc/parser.y via crafted COBOL source code.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Gnucobol Project Gnucobol.

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

Upgrade to a fixed version.

## Is CVE-2019-16396 being exploited?

There is no known exploitation of CVE-2019-16396 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2019-16395](https://insights.sbomify.com/CVE-2019-16395/): Memory corruption in n/a (high 7.8)
- [CVE-2019-14528](https://insights.sbomify.com/CVE-2019-14528/): Memory corruption in n/a (high 7.8)
- [CVE-2019-14541](https://insights.sbomify.com/CVE-2019-14541/): Memory corruption in n/a (high 7.8)
- [CVE-2019-14468](https://insights.sbomify.com/CVE-2019-14468/): Memory corruption in n/a (high 7.8)
- [CVE-2019-14486](https://insights.sbomify.com/CVE-2019-14486/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16396 is a high-severity use after free vulnerability in n/a, published on 17 Sep 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-16396 in the wild and no public exploit code.

Affected product: n/a. 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-16396/ (Markdown: https://insights.sbomify.com/CVE-2019-16396/index.md)
```

## Sources

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

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