# OSV-2024-309: Use-of-uninitialized-value in fast_forward_first_n_chars

> A use-of-uninitialized-value bug in PCRE2's JIT compiler can cause crashes, potentially leading to denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2024

## What is OSV-2024-309?

OSV-2024-309 is a vulnerability in pcre2, published on 29 Apr 2024. 

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=66944

```
Crash type: Use-of-uninitialized-value
Crash state:
fast_forward_first_n_chars
jit_compile
pcre2_jit_compile_8
```

## Which versions are affected by OSV-2024-309?

1 open source package ship an affected version, including pcre2.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pcre2` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2024-309?

No fix has been published for OSV-2024-309 yet. Limit exposure of the affected software until one is available.

## Is OSV-2024-309 being exploited?

There is no known exploitation of OSV-2024-309 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2024-309 and fix it if it is affected.

What it is: OSV-2024-309 is a vulnerability in pcre2, published on 29 Apr 2024. 
Exploitation: There is no known exploitation of OSV-2024-309 in the wild and no public exploit code.

Affected packages and fixed versions:
- pcre2 (OSS-Fuzz): affected all versions; no fix listed

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/OSV-2024-309/ (Markdown: https://insights.sbomify.com/OSV-2024-309/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2024-309

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