# openSUSE-SU-2022:10209-1: Security update for tor

> An attacker can cause denial of service against Tor network nodes by exploiting circuit queue handling and DNS cache weaknesses.

- **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 Nov 2022

## What is openSUSE-SU-2022:10209-1?

openSUSE-SU-2022:10209-1 is a denial of service vulnerability in tor, published on 20 Nov 2022. 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 0.4.7.11:

  * Improve security of DNS cache by randomly clipping the TTL
    value (boo#1205307, TROVE-2021-009)
  * Improved defenses against network-wide DoS, multiple counters
    and metrics added to MetricsPorts
  * Apply circuit creation anti-DoS defenses if the outbound
    circuit max cell queue size is reached too many times. This
    introduces two new consensus parameters to control the queue
    size limit and number of times allowed to go over that limit.
  * Directory authority updates
  * IPFire database and geoip updates
  * Bump the maximum amount of CPU that can be used from 16 to 128.
    The NumCPUs torrc option overrides this hardcoded maximum.
  * onion service: set a higher circuit build timeout for opened
    client rendezvous circuit to avoid timeouts and retry load
  * Make the service retry a rendezvous if the circuit is being
    repurposed for measurements

## Which versions are affected by openSUSE-SU-2022:10209-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tor` | SUSE:Package Hub 15 SP3 | All versions | 0.4.7.11-bp154.2.9.1 |
| `tor` | SUSE:Package Hub 15 SP4 | All versions | 0.4.7.11-bp154.2.9.1 |
| `tor` | openSUSE:Leap 15.3 | All versions | 0.4.7.11-bp154.2.9.1 |
| `tor` | openSUSE:Leap 15.4 | All versions | 0.4.7.11-bp154.2.9.1 |

## How do I fix openSUSE-SU-2022:10209-1?

Upgrade to a fixed version.

## Is openSUSE-SU-2022:10209-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: openSUSE-SU-2022:10209-1 is a denial of service vulnerability in tor, published on 20 Nov 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 openSUSE-SU-2022:10209-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-2022-10209-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2022-10209-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2022:10209-1

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