# openSUSE-SU-2023:0361-1: Security update for tor > A remote attacker can cause a denial of service by crashing Tor instances compiled with OpenSSL during handshake. - **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:** 10 Nov 2023 ## What is openSUSE-SU-2023:0361-1? openSUSE-SU-2023:0361-1 is a denial of service vulnerability in tor, published on 10 Nov 2023. 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.8.8: * Mitigate an issue when Tor compiled with OpenSSL can crash during handshake with a remote relay. (TROVE-2023-004, boo#1216873) * Regenerate fallback directories generated on November 03, 2023. * Update the geoip files to match the IPFire Location Database, as retrieved on 2023/11/03 * directory authority: Look at the network parameter 'maxunmeasuredbw' with the correct spelling * vanguards addon support: Count the conflux linked cell as valid when it is successfully processed. This will quiet a spurious warn in the vanguards addon - tor 0.4.8.7: * Fix an issue that prevented us from pre-building more conflux sets after existing sets had been used - tor 0.4.8.6: * onion service: Fix a reliability issue where services were expiring their introduction points every consensus update. This caused connectivity issues for clients caching the old descriptor and intro points * Log the input and output buffer sizes when we detect a potential compression bomb * Disable multiple BUG warnings of a missing relay identity key when starting an instance of Tor compiled without relay support * When reporting a pseudo-networkstatus as a bridge authority, or answering 'ns/purpose/*' controller requests, include accurate published-on dates from our list of router descriptors * Use less frightening language and lower the log-level of our run-time ABI compatibility check message in our Zstd compression subsystem - tor 0.4.8.5: * bugfixes creating log BUG stacktrace - tor 0.4.8.4: * Extend DoS protection to partially opened channels and known relays * Dynamic Proof-Of-Work protocol to thwart flooding DoS attacks against hidden services. Disabled by default, enable via 'HiddenServicePoW' in torrc * Implement conflux traffic splitting * Directory authorities and relays now interact properly with directory authorities if they change addresses - tor 0.4.7.14: * bugfix affecting vanguards (onion service), and minor fixes - Enable support for scrypt() ## Which versions are affected by openSUSE-SU-2023:0361-1? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `tor` | SUSE:Package Hub 15 SP4 | All versions | 0.4.8.8-bp155.2.3.1 | | `tor` | SUSE:Package Hub 15 SP5 | All versions | 0.4.8.8-bp155.2.3.1 | | `tor` | openSUSE:Leap 15.4 | All versions | 0.4.8.8-bp155.2.3.1 | | `tor` | openSUSE:Leap 15.5 | All versions | 0.4.8.8-bp155.2.3.1 | ## How do I fix openSUSE-SU-2023:0361-1? Upgrade to a fixed version. ## Is openSUSE-SU-2023:0361-1 being exploited? There is no known exploitation of openSUSE-SU-2023:0361-1 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for openSUSE-SU-2023:0361-1 and fix it if it is affected. What it is: openSUSE-SU-2023:0361-1 is a denial of service vulnerability in tor, published on 10 Nov 2023. 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-2023:0361-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-2023-0361-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2023-0361-1/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/openSUSE-SU-2023:0361-1 --- From sbomify Insights: https://insights.sbomify.com/openSUSE-SU-2023-0361-1/ Summaries are generated and may contain mistakes; the official description above is the record.