# GHSA-3p92-886g-qxpq: Remote Memory Exposure in floody

> Remote attackers can expose uninitialized memory by passing a number to the write method, potentially leaking sensitive data.

- **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:** 4 Jun 2019

## What is GHSA-3p92-886g-qxpq?

GHSA-3p92-886g-qxpq is a vulnerability in floody, published on 4 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `floody` before 0.1.1 are vulnerable to remote memory exposure.

.write(number)` in the affected `floody` versions passes a number to Buffer constructor, appending a chunk of uninitialized memory.

Proof of Concept: 

```
var f = require('floody')(process.stdout); 
f.write(USERSUPPLIEDINPUT); 
'f.stop();

## Recommendation

Update to version 0.1.1 or later.

## Which versions are affected by GHSA-3p92-886g-qxpq?

2 open source packages ship an affected version, including floody.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `floody` | npm | All versions | 0.1.1 |
| `floody` | npm | All versions | 0.1.1 |

## How do I fix GHSA-3p92-886g-qxpq?

Upgrade floody to 0.1.1 or later.

## Is GHSA-3p92-886g-qxpq being exploited?

There is no known exploitation of GHSA-3p92-886g-qxpq in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-3p92-886g-qxpq and fix it if it is affected.

What it is: GHSA-3p92-886g-qxpq is a vulnerability in floody, published on 4 Jun 2019. 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-3p92-886g-qxpq in the wild and no public exploit code.

Affected packages and fixed versions:
- floody (npm): affected all versions; fixed in 0.1.1
- floody (npm): affected all versions; fixed in 0.1.1

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-3p92-886g-qxpq/ (Markdown: https://insights.sbomify.com/GHSA-3p92-886g-qxpq/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-3p92-886g-qxpq

---
From sbomify Insights: https://insights.sbomify.com/GHSA-3p92-886g-qxpq/
Summaries are generated and may contain mistakes; the official description above is the record.