# GHSA-j79x-vvgm-w73w: bottlerocket dependency openssl provides streaming of ASN.1 data via a BIO

> A use-after-free vulnerability in OpenSSL's ASN.1 BIO streaming allows attackers to cause application crashes via malicious input.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Feb 2023

## What is GHSA-j79x-vvgm-w73w?

GHSA-j79x-vvgm-w73w is an use after free vulnerability in bottlerocket/update-operator, published on 9 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An OpenSSL public API provides streaming of ASN.1 data via a BIO. It is possible for a malicious third party to use the BIO to access unfreed memory pointers that are not cleaned up after execution of the API. Freeing these memory pointers will result in a crash. Agents and clients compiled with OpenSSL may see unexpected crashes. OpenSSL has been removed in bottlerocket/update-operator version 1.1.0 in favor of Rust-based TLS using rustls.

## Which versions are affected by GHSA-j79x-vvgm-w73w?

1 open source package ship an affected version, including bottlerocket/update-operator.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `bottlerocket/update-operator` | crates.io | All versions | 1.1.0 |

## How do I fix GHSA-j79x-vvgm-w73w?

Upgrade bottlerocket/update-operator to 1.1.0 or later.

## Is GHSA-j79x-vvgm-w73w being exploited?

There is no known exploitation of GHSA-j79x-vvgm-w73w in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-j79x-vvgm-w73w and fix it if it is affected.

What it is: GHSA-j79x-vvgm-w73w is an use after free vulnerability in bottlerocket/update-operator, published on 9 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-j79x-vvgm-w73w in the wild and no public exploit code.

Affected packages and fixed versions:
- bottlerocket/update-operator (crates.io): affected all versions; fixed in 1.1.0

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/GHSA-j79x-vvgm-w73w/ (Markdown: https://insights.sbomify.com/GHSA-j79x-vvgm-w73w/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-j79x-vvgm-w73w

---
From sbomify Insights: https://insights.sbomify.com/GHSA-j79x-vvgm-w73w/
Summaries are generated and may contain mistakes; the official description above is the record.