# SUSE-SU-2022:0729-1: Security update for SUSE Manager Server 4.2

> A null pointer exception in SUSE Manager Server during Ubuntu errata synchronization can cause a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Mar 2022

## What is SUSE-SU-2022:0729-1?

SUSE-SU-2022:0729-1 is a vulnerability in spacewalk-java, published on 4 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update fixes the following issues:

spacewalk-java:

- Version 4.2.33-1
  * handle npe when syncing ubuntu errata (bsc#1196619)

susemanager-sync-data:

- Version 4.2.11-1
  * change centos 8 eol urls to vault which still work

How to apply this update:

1. Log in as root user to the SUSE Manager server.
2. Stop the Spacewalk service:
`spacewalk-service stop`
3. Apply the patch using either zypper patch or YaST Online Update.
4. Start the Spacewalk service:
`spacewalk-service start`

## Which versions are affected by SUSE-SU-2022:0729-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `spacewalk-java` | SUSE:Manager Server Module 4.2 | All versions | 4.2.33-150300.3.23.1 |
| `susemanager-sync-data` | SUSE:Manager Server Module 4.2 | All versions | 4.2.11-150300.3.15.1 |

## How do I fix SUSE-SU-2022:0729-1?

Apply the vendor's patch.

## Is SUSE-SU-2022:0729-1 being exploited?

There is no known exploitation of SUSE-SU-2022:0729-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2022:0729-1 and fix it if it is affected.

What it is: SUSE-SU-2022:0729-1 is a vulnerability in spacewalk-java, published on 4 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2022:0729-1 in the wild and no public exploit code.

Affected product: spacewalk-java. 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/SUSE-SU-2022-0729-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2022-0729-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2022:0729-1

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