# OSV-2018-79: Use-of-uninitialized-value in g_dbus_message_new_from_blob

> An attacker can cause a denial of service in applications using the GLib D-Bus library by triggering a use-of-uninitialized-value error during message parsing.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2021

## What is OSV-2018-79?

OSV-2018-79 is a vulnerability in glib, published on 13 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9825

```
Crash type: Use-of-uninitialized-value
Crash state:
g_dbus_message_new_from_blob
fuzz_dbus_message.c
g_dbus_message_new_from_blob
```

## Which versions are affected by OSV-2018-79?

1 open source package ship an affected version, including glib.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `glib` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2018-79?

No fix has been published for OSV-2018-79 yet. Limit exposure of the affected software until one is available.

## Is OSV-2018-79 being exploited?

There is no known exploitation of OSV-2018-79 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2018-79 and fix it if it is affected.

What it is: OSV-2018-79 is a vulnerability in glib, published on 13 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of OSV-2018-79 in the wild and no public exploit code.

Affected packages and fixed versions:
- glib (OSS-Fuzz): affected all versions; no fix listed

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/OSV-2018-79/ (Markdown: https://insights.sbomify.com/OSV-2018-79/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2018-79

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