# CVE-2021-39359: Security feature bypass in n/a

> An attacker can perform man-in-the-middle attacks against applications using libgda because TLS certificate verification is disabled by default.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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:** 22 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2021-39359, GHSA-p8hp-p5rw-j34r, MGASA-2022-0005, SUSE-SU-2022:3016-1, UBUNTU-CVE-2021-39359, openSUSE-SU-2024:11803-1

## What is CVE-2021-39359?

CVE-2021-39359 is a medium-severity vulnerability in Fedoraproject Fedora, published on 22 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In GNOME libgda through 6.0.0, gda-web-provider.c does not enable TLS certificate verification on the SoupSessionSync objects it creates, leaving users vulnerable to network MITM attacks. NOTE: this is similar to CVE-2016-20011.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2021-39359?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libgda` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 5.2.4-9.3.1 |
| `libgda` | SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 5.2.4-9.3.1 |
| `libgda` | SUSE:Linux Enterprise Server 12 SP4-LTSS | All versions | 5.2.4-9.3.1 |
| `libgda` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 5.2.4-9.3.1 |
| `libgda` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 5.2.4-9.3.1 |
| `libgda` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 5.2.4-9.3.1 |
| `libgda` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 5.2.4-9.3.1 |
| `libgda` | SUSE:Linux Enterprise Workstation Extension 12 SP5 | All versions | 5.2.4-9.3.1 |
| `libgda` | SUSE:OpenStack Cloud 9 | All versions | 5.2.4-9.3.1 |
| `libgda` | SUSE:OpenStack Cloud Crowbar 9 | All versions | 5.2.4-9.3.1 |

Products: Fedoraproject Fedora, Gnome Libgda.

## How do I fix CVE-2021-39359?

Apply the vendor's patch.

## Is CVE-2021-39359 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-39359 and fix it if it is affected.

What it is: CVE-2021-39359 is a medium-severity vulnerability in Fedoraproject Fedora, published on 22 Aug 2021. 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-2021-39359 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. 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-2021-39359/ (Markdown: https://insights.sbomify.com/CVE-2021-39359/index.md)
```

## Sources

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

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