# SUSE-SU-2018:2902-2: Security update for yast2-smt

> This update addresses configuration and translation issues in yast2-smt, required for a separate SMT security fix.

- **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:** 18 Oct 2018

## What is SUSE-SU-2018:2902-2?

SUSE-SU-2018:2902-2 is a vulnerability in yast2-smt, published on 18 Oct 2018. 

### Official description

This update fixes the following issues in yast2-smt:

- Explicitly mention 'Organization Credentials' (fate#321759)
- Rearrange the SMT set-up dialog (bsc#977043)
- Added missing translation marks (bsc#1037811)
- Remove cron job rescheduling (bsc#1097560)

This update is a requirement for the security update for SMT. Because of that it is
tagged as security to ensure that all users, even those that only install security updates,
install it.

## Which versions are affected by SUSE-SU-2018:2902-2?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `yast2-smt` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 3.0.14-17.3.2 |

## How do I fix SUSE-SU-2018:2902-2?

Apply the vendor's patch.

## Is SUSE-SU-2018:2902-2 being exploited?

There is no known exploitation of SUSE-SU-2018:2902-2 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2018:2902-2 and fix it if it is affected.

What it is: SUSE-SU-2018:2902-2 is a vulnerability in yast2-smt, published on 18 Oct 2018. 
Exploitation: There is no known exploitation of SUSE-SU-2018:2902-2 in the wild and no public exploit code.

Affected product: yast2-smt. 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-2018-2902-2/ (Markdown: https://insights.sbomify.com/SUSE-SU-2018-2902-2/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2018:2902-2

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