# openSUSE-SU-2023:0087-1: Security update for seamonkey

> An attacker can execute arbitrary code or escalate privileges by exploiting multiple backported security flaws in the SeaMonkey browser suite.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Apr 2023

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

openSUSE-SU-2023:0087-1 is a vulnerability in seamonkey, published on 11 Apr 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

SeaMonkey was updated to 2.53.16:

* No throbber in plaintext editor bug 85498.
* Remove unused gridlines class from EdAdvancedEdit bug 1806632.
* Remove ESR 91 links from debugQA bug 1804534.
* Rename devtools/shim to devtools/startup bug 1812367.
* Remove unused seltype=text|cell css bug 1806653.
* Implement new shared tree styling bug 1807802.
* Use `win.focus()` in macWindowMenu.js bug 1807817.
* Remove WCAP provider bug 1579020.
* Remove ftp/file tree view support bug 1239239.
* Change calendar list tree to a list bug 1561530.
* Various other updates to the calendar code.
* Continue the switch from Python 2 to Python 3 in the build system.
* Verified compatibility with Rust 1.66.1.
* SeaMonkey 2.53.16 uses the same backend as Firefox and contains
  the relevant Firefox 60.8 security fixes.
* SeaMonkey 2.53.16 shares most parts of the mail and news code with
  Thunderbird. Please read the Thunderbird 60.8.0 release notes for
  specific security fixes in this release.
* Additional important security fixes up to Current Firefox 102.9
  and Thunderbird 102.9 ESR plus many enhancements have been
  backported. We will continue to enhance SeaMonkey security in
  subsequent 2.53.x beta and release versions as fast as we are able
  to.

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `seamonkey` | SUSE:Package Hub 15 SP4 | All versions | 2.53.16-bp154.2.6.2 |
| `seamonkey` | openSUSE:Leap 15.4 | All versions | 2.53.16-bp154.2.6.2 |

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

Upgrade to a fixed version.

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

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

## Fix prompt for AI coding agents

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

What it is: openSUSE-SU-2023:0087-1 is a vulnerability in seamonkey, published on 11 Apr 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of openSUSE-SU-2023:0087-1 in the wild and no public exploit code.

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

## Sources

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

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