# CVE-2020-36774: Denial of service in n/a

> An attacker can cause a denial of service via application crash in GNOME Glade due to improper widget rebuilding handling.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Feb 2024
- **Updated:** 4 Sep 2024
- **Also known as:** DEBIAN-CVE-2020-36774, GHSA-j9jp-j2w9-gw9c, OESA-2024-1270, OESA-2024-1309, SUSE-SU-2024:0983-1, UBUNTU-CVE-2020-36774, openSUSE-SU-2024:13737-1

## What is CVE-2020-36774?

CVE-2020-36774 is a medium-severity denial of service vulnerability in n/a, published on 19 Feb 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

plugins/gtk+/glade-gtk-box.c in GNOME Glade before 3.38.1 and 3.39.x before 3.40.0 mishandles widget rebuilding for GladeGtkBox, leading to a denial of service (application crash).

Weakness: CWE-664 (Improper Control of a Resource Through its Lifetime)

## Which versions are affected by CVE-2020-36774?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `glade` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 3.20.0-7.3.1 |

Products: Gnome Glade.

## How do I fix CVE-2020-36774?

Upgrade to a fixed version.

## Is CVE-2020-36774 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-36774 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36774 and fix it if it is affected.

What it is: CVE-2020-36774 is a medium-severity denial of service vulnerability in n/a, published on 19 Feb 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-36774 exists.

Affected product: n/a. 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-2020-36774/ (Markdown: https://insights.sbomify.com/CVE-2020-36774/index.md)
```

## Sources

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

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