# openSUSE-SU-2021:1050-1: Security update for fossil

> Security update for Fossil SCM fixes TLS hostname verification and other issues, requiring users to upgrade to the latest version.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 17 Jul 2021

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

openSUSE-SU-2021:1050-1 is a vulnerability in fossil, published on 17 Jul 2021. 

### Official description

This update for fossil fixes the following issues:

fossil 2.16:

  * Add the fossil patch command
  * Improve the fossil ui command to work on check-out directories
    and remote machines
  * web UI improvements
  * Add fossil bisect run command for improved automation of bisects
  * Improve fossil merge handling of renames
  * wiki now defaults to markdown
  * email alerts can now be set to expire to prevent sending mail
    to abandoned accounts forever

fossil 2.15.2:

  * Fix the client-side TLS so that it verifies that the server
    hostname matches its certificate (boo#1187988)

fossil 2.15.1:

  * fix access to tables starting 'fx_' in ticket report

fossil 2.15:

  * Relax default Content Security policy to allow images to be
    loaded from any URL
  * Updates to skins and their configuration options
  * Built-in skin can now be selected via the skin= request
    parameter and the /skins page.
  * /cookies page can now now  delete individual cookies
  * Various extensions to diff displaz and operations
  * Add the --list option to the tarball, zip, and sqlar commands.
  * New TH1 commands: 'builtin_request_js', 'capexpr', 'foreach',
    'lappend', and 'string match'
  * The leaves command now shows the branch point of each leaf.
  * The fossil add command refuses to add files whose names are
    reserved by Windows (ex: 'aux') unless the --allow-reserved
    option is included.

fossil 2.14

  * add fossil chat
  * enhanced fossil clone
  * performance optimization
  * enhanced documents
  * Pikchr improvements
  * Schema Update Notice #1: This release drops a trigger from 
  the database schema
  * Schema Update Notice #2: This release changes how the descriptions
  of wiki edits are stored in the EVENT table, for improved display
  on timelines

fossil 2.13:

  * wiki improvements: interwiki links, markup features
  * support for rendering pikchr markup scriptions
  * line number modes support interactive selection of range of
    lines to hyperlink to
  * Enhance finfo page to track a file across renames
- minimum/bundled version of sqlite increased to 3.34.0

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fossil` | SUSE:Package Hub 15 SP3 | All versions | 2.16-bp153.2.3.1 |
| `fossil` | openSUSE:Leap 15.3 | All versions | 2.16-bp153.2.3.1 |

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

Upgrade to a fixed version.

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

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

## Fix prompt for AI coding agents

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

What it is: openSUSE-SU-2021:1050-1 is a vulnerability in fossil, published on 17 Jul 2021. 
Exploitation: There is no known exploitation of openSUSE-SU-2021:1050-1 in the wild and no public exploit code.

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

## Sources

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

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