# CVE-2016-1000033: Weak cryptography in n/a

> Shotwell fails to validate TLS certificates, allowing attackers to perform man-in-the-middle attacks and intercept or modify data.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Oct 2016
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-1000033, GHSA-9hvv-q3hq-r4f2

## What is CVE-2016-1000033?

CVE-2016-1000033 is a low-severity vulnerability in Redhat Enterprise Linux, published on 25 Oct 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Shotwell version 0.22.0 (and possibly other versions) is vulnerable to a TLS/SSL certification validation flaw resulting in a potential for man in the middle attacks.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2016-1000033?

It affects 2 products.


Products: Gnome Shotwell, Redhat Enterprise Linux.

## How do I fix CVE-2016-1000033?

Upgrade to a fixed version.

## Is CVE-2016-1000033 being exploited?

There is no known exploitation of CVE-2016-1000033 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2017-1000024](https://insights.sbomify.com/CVE-2017-1000024/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1000033 and fix it if it is affected.

What it is: CVE-2016-1000033 is a low-severity vulnerability in Redhat Enterprise Linux, published on 25 Oct 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-1000033 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux. 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/CVE-2016-1000033/ (Markdown: https://insights.sbomify.com/CVE-2016-1000033/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-1000033
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-1000033
- OSV: https://osv.dev/vulnerability/CVE-2016-1000033

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-1000033/
Summaries are generated and may contain mistakes; the official description above is the record.