OSV-2022-808 Use-of-uninitialized-value in _dbus_marshal_write_basic
Not scored
Published
Check this codebase for OSV-2022-808 and fix it if it is affected.
What it is: OSV-2022-808 is a vulnerability in cras, published on 31 Aug 2022.
Exploitation: There is no known exploitation of OSV-2022-808 in the wild and no public exploit code.
Affected packages and fixed versions:
- cras (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-2022-808/ (Markdown: https://insights.sbomify.com/OSV-2022-808/index.md)
An uninitialized value in D-Bus marshaling can cause a crash, potentially leading to denial of service for applications using the library.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is OSV-2022-808?
OSV-2022-808 is a vulnerability in cras, published on 31 Aug 2022.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50762
Crash type: Use-of-uninitialized-value
Crash state:
_dbus_marshal_write_basic
_dbus_type_writer_write_basic
write_basic_field
Which versions are affected by OSV-2022-808?
1 open source package ship an affected version, including cras.
| Package | Affected | Fixed in |
|---|---|---|
cras OSS-Fuzz | All versions | None |
How do I fix OSV-2022-808?
No fix has been published for OSV-2022-808 yet. Limit exposure of the affected software until one is available.
Is OSV-2022-808 being exploited?
There is no known exploitation of OSV-2022-808 in the wild and no public exploit code.