# openSUSE-SU-2021:0316-1: Security update for tor

> An update to Tor fixes undefined behavior in Keccak and improves relay circuit checks, preventing potential crashes or network manipulation.

- **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:** 20 Feb 2021

## What is openSUSE-SU-2021:0316-1?

openSUSE-SU-2021:0316-1 is a vulnerability in tor, published on 20 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for tor fixes the following issues:

tor was updated to 0.4.5.6:

* https://lists.torproject.org/pipermail/tor-announce/2021-February/000214.html
* Introduce a new MetricsPort HTTP interface
* Support IPv6 in the torrc Address option
* Add event-tracing library support for USDT and LTTng-UST
* Try to read N of N bytes on a TLS connection

tor was updated to 0.4.4.7:

* https://blog.torproject.org/node/1990
* Stop requiring a live consensus for v3 clients and services
* Re-entry into the network is now denied at the Exit level
* Fix undefined behavior on our Keccak library
* Strip '\r' characters when reading text files on Unix platforms
* Handle partial SOCKS5 messages correctly

* Check channels+circuits on relays more thoroughly (TROVE-2020-005, boo#1178741)

## Which versions are affected by openSUSE-SU-2021:0316-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tor` | openSUSE:Leap 15.2 | All versions | 0.4.5.6-lp152.2.6.1 |

## How do I fix openSUSE-SU-2021:0316-1?

Upgrade to a fixed version.

## Is openSUSE-SU-2021:0316-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: openSUSE-SU-2021:0316-1 is a vulnerability in tor, published on 20 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of openSUSE-SU-2021:0316-1 in the wild and no public exploit code.

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

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2021:0316-1

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