# OSV-2023-715: Stack-use-after-scope in ulocimp_addLikelySubtags_74

> A stack-use-after-scope vulnerability in the ICU library's locale handling allows attackers to potentially execute code or cause 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:** 21 Aug 2023

## What is OSV-2023-715?

OSV-2023-715 is an use after free vulnerability in icu, published on 21 Aug 2023. 

### Official description

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

```
Crash type: Stack-use-after-scope READ 3
Crash state:
ulocimp_addLikelySubtags_74
uloc_isRightToLeft_74
uloc_is_right_to_left_fuzzer.cpp
```

## Which versions are affected by OSV-2023-715?

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


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

## How do I fix OSV-2023-715?

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

## Is OSV-2023-715 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2023-715 and fix it if it is affected.

What it is: OSV-2023-715 is an use after free vulnerability in icu, published on 21 Aug 2023. 
Exploitation: There is no known exploitation of OSV-2023-715 in the wild and no public exploit code.

Affected packages and fixed versions:
- icu (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-2023-715/ (Markdown: https://insights.sbomify.com/OSV-2023-715/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2023-715

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