# openSUSE-SU-2020:0368-1: Security update for texlive-filesystem

> Local attackers can exploit race conditions in TeX Live file handling to escalate privileges or cause denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Mar 2020

## What is openSUSE-SU-2020:0368-1?

openSUSE-SU-2020:0368-1 is a vulnerability in texlive-filesystem, published on 23 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This update for texlive-filesystem fixes the following issues:

Security issues fixed:

- Changed default user for ls-R files and font cache directories to user nobody (bsc#1159740) 
- Switched to rm instead of safe-rm or safe-rmdir to avoid race conditions (bsc#1158910) .
- Made cron script more failsafe (bsc#1150556)

Non-security issue fixed:

- Refreshed font map files on update (bsc#1155381) 

This update was imported from the SUSE:SLE-15:Update update project.

## Which versions are affected by openSUSE-SU-2020:0368-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `texlive-filesystem` | openSUSE:Leap 15.1 | All versions | 2017.135-lp151.8.3.1 |

## How do I fix openSUSE-SU-2020:0368-1?

Apply the vendor's patch.

## Is openSUSE-SU-2020:0368-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: openSUSE-SU-2020:0368-1 is a vulnerability in texlive-filesystem, published on 23 Mar 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of openSUSE-SU-2020:0368-1 in the wild and no public exploit code.

Affected product: texlive-filesystem. 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-2020-0368-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2020-0368-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2020:0368-1

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