# openSUSE-SU-2023:0270-1: Security update for Cadence

> Cadence software contains vulnerabilities related to fixed temporary files, potentially allowing local attackers to escalate privileges or modify data.

- **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:** 25 Sep 2023

## What is openSUSE-SU-2023:0270-1?

openSUSE-SU-2023:0270-1 is a vulnerability in Cadence, published on 25 Sep 2023. 

### Official description

This update for Cadence fixes the following issues:

- Fix security bugs related to use of Fixed Temporary Files.
  (boo#1213330, boo#1213983, boo#1213985)

## Which versions are affected by openSUSE-SU-2023:0270-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Cadence` | SUSE:Package Hub 15 SP4 | All versions | 0.9.1-bp154.2.3.1 |
| `Cadence` | openSUSE:Leap 15.4 | All versions | 0.9.1-bp154.2.3.1 |

## How do I fix openSUSE-SU-2023:0270-1?

Apply the vendor's patch.

## Is openSUSE-SU-2023:0270-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: openSUSE-SU-2023:0270-1 is a vulnerability in Cadence, published on 25 Sep 2023. 
Exploitation: There is no known exploitation of openSUSE-SU-2023:0270-1 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2023:0270-1

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