# openSUSE-SU-2019:2607-1: Recommended update for openafs

> OpenAFS server RPC handling flaws allow attackers to cause memory corruption, potentially leading to code execution or denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Dec 2019

## What is openSUSE-SU-2019:2607-1?

openSUSE-SU-2019:2607-1 is a memory corruption vulnerability in openafs, published on 1 Dec 2019. It can be exploited over the network, with no action from the victim.

### Official description

This update for openafs fixes the following issues:

Update to security-release 1.8.5, adresses:

* OPENAFS-SA-2019-001: Skip server OUT args on error 
* OPENAFS-SA-2019-002: Zero all server RPC args
* OPENAFS-SA-2019-003: ubik: Avoid unlocked ubik_currentTrans deref

update to official version 1.8.4 

* support Linux-kernel 5.3
* Avoid non-dir ENOENT errors in afs_lookup
* fix parsing of fileservers with -vlruthresh, etc.
* other bugfixes  

update to pre-release 1.8.4pre2

* fix builds for Linux-kernels 5.3

update to 1.8.3

- fix broken directory layout
- allow crypt to be set/unset on startup of client

update to pre-release 1.8.3pre1

* fix builds for Linux-kernels 4.20 and 5.0 
* other fixes, see RELNOTES-1.8.3pre1

## Which versions are affected by openSUSE-SU-2019:2607-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openafs` | openSUSE:Leap 15.1 | All versions | 1.8.5-lp151.2.3.1 |

## How do I fix openSUSE-SU-2019:2607-1?

Upgrade to a fixed version.

## Is openSUSE-SU-2019:2607-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: openSUSE-SU-2019:2607-1 is a memory corruption vulnerability in openafs, published on 1 Dec 2019. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of openSUSE-SU-2019:2607-1 in the wild and no public exploit code.

Affected product: openafs. 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-2019-2607-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2019-2607-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2019:2607-1

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