# OSV-2022-331: Stack-buffer-overflow in void unwindstack::Symbols::BuildRemapTable > A stack-buffer-overflow in the unwindstack library allows attackers to cause denial of service or potentially execute code via crafted ELF files. - **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:** 11 Apr 2022 ## What is OSV-2022-331? OSV-2022-331 is a memory corruption vulnerability in perfetto, published on 11 Apr 2022. ### Official description OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=46546 Crash type: Stack-buffer-overflow READ {*} Crash state: void unwindstack::Symbols::BuildRemapTable bool unwindstack::Symbols::GetName unwindstack::ElfInterfaceImpl::GetFunctionName ## Which versions are affected by OSV-2022-331? 1 open source package ship an affected version, including perfetto. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `perfetto` | OSS-Fuzz | All versions | None | ## How do I fix OSV-2022-331? No fix has been published for OSV-2022-331 yet. Limit exposure of the affected software until one is available. ## Is OSV-2022-331 being exploited? There is no known exploitation of OSV-2022-331 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for OSV-2022-331 and fix it if it is affected. What it is: OSV-2022-331 is a memory corruption vulnerability in perfetto, published on 11 Apr 2022. Exploitation: There is no known exploitation of OSV-2022-331 in the wild and no public exploit code. Affected packages and fixed versions: - perfetto (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-2022-331/ (Markdown: https://insights.sbomify.com/OSV-2022-331/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/OSV-2022-331 --- From sbomify Insights: https://insights.sbomify.com/OSV-2022-331/ Summaries are generated and may contain mistakes; the official description above is the record.