# openSUSE-SU-2021:0207-1: Security update for segv_handler

> The segv_handler package was removed from openSUSE for security reasons, requiring users to update their systems to remove the vulnerable component.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 30 Jan 2021

## What is openSUSE-SU-2021:0207-1?

openSUSE-SU-2021:0207-1 is a vulnerability in segv_handler, published on 30 Jan 2021. 

### Official description

This update for segv_handler fixes the following issues:

- Replace by empty package with README explaining the removal for security
  reasons (boo#1180665).

## Which versions are affected by openSUSE-SU-2021:0207-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `segv_handler` | openSUSE:Leap 15.2 | All versions | 0.0.1-lp152.4.3.1 |

## How do I fix openSUSE-SU-2021:0207-1?

Apply the vendor's patch.

## Is openSUSE-SU-2021:0207-1 being exploited?

There is no known exploitation of openSUSE-SU-2021:0207-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for openSUSE-SU-2021:0207-1 and fix it if it is affected.

What it is: openSUSE-SU-2021:0207-1 is a vulnerability in segv_handler, published on 30 Jan 2021. 
Exploitation: There is no known exploitation of openSUSE-SU-2021:0207-1 in the wild and no public exploit code.

Affected product: segv_handler. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/openSUSE-SU-2021-0207-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2021-0207-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2021:0207-1

---
From sbomify Insights: https://insights.sbomify.com/openSUSE-SU-2021-0207-1/
Summaries are generated and may contain mistakes; the official description above is the record.