# openSUSE-SU-2024:0329-1: Security update for seamonkey

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

- **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:** 9 Oct 2024

## What is openSUSE-SU-2024:0329-1?

openSUSE-SU-2024:0329-1 is a vulnerability in seamonkey, published on 9 Oct 2024. 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

This update for seamonkey fixes the following issues:

update to SeaMonkey 2.53.19:

  * Cancel button in SeaMonkey bookmarking star ui not working bug
    1872623.
  * Remove OfflineAppCacheHelper.jsm copy from SeaMonkey and use the
    one in toolkit bug 1896292.
  * Remove obsolete registerFactoryLocation calls from cZ bug 1870930.
  * Remove needless implements='nsIDOMEventListener' and QI bug
    1611010.
  * Replace use of nsIStandardURL::Init bug 1864355.
  * Switch SeaMonkey website from hg.mozilla.org to heptapod. bug
    1870934.
  * Allow view-image to open a data: URI by setting a flag on the
    loadinfo bug 1877001.
  * Save-link-as feature should use the loading principal and context
    menu using nsIContentPolicy.TYPE_SAVE_AS_DOWNLOAD bug 1879726.
  * Use punycode in SeaMonkey JS bug 1864287.
  * Font lists in preferences are no longer grouped by font type, port
    asynchronous handling like Bug 1399206 bug 1437393.
  * SeaMonkey broken tab after undo closed tab with invalid protocol
    bug 1885748.
  * SeaMonkey session restore is missing the checkboxes in the Classic
    theme bug 1896174.
  * Implement about:credits on seamonkey-project.org website bug
    1898467.
  * Fix for the 0.0.0.0 day vulnerability oligo summary.
  * Link in update notification does not open Browser bug 1888364.
  * Update ReadExtensionPrefs in Preferences.cpp bug 1890196.
  * Add about:seamonkey page to SeaMonkey bug 1897801.
  * SeaMonkey 2.53.19 uses the same backend as Firefox and contains
    the relevant Firefox 60.8 security fixes.
  * SeaMonkey 2.53.19 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 115.14
    and Thunderbird 115.14 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-2024:0329-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `seamonkey` | SUSE:Package Hub 15 SP6 | All versions | 2.53.19-bp156.2.3.1 |
| `seamonkey` | openSUSE:Leap 15.6 | All versions | 2.53.19-bp156.2.3.1 |

## How do I fix openSUSE-SU-2024:0329-1?

Upgrade to a fixed version.

## Is openSUSE-SU-2024:0329-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: openSUSE-SU-2024:0329-1 is a vulnerability in seamonkey, published on 9 Oct 2024. 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-2024:0329-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-2024-0329-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2024-0329-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2024:0329-1

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