CVE-2017-6355 Integer overflow in the vrend_create_shader function in vrend_renderer.c in virglrenderer before 0.6.0 allows local guest OS users to cause
Medium 5.5
Published
Updated
Check this codebase for CVE-2017-6355 and fix it if it is affected.
What it is: CVE-2017-6355 is a medium-severity vulnerability in n/a, published on 10 Mar 2017.
Exploitation: There is no known exploitation of CVE-2017-6355 in the wild and no public exploit code.
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-2017-6355/ (Markdown: https://insights.sbomify.com/CVE-2017-6355/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2017-6355?
CVE-2017-6355 is a medium-severity vulnerability in n/a, published on 10 Mar 2017.
Official description
Integer overflow in the vrend_create_shader function in vrend_renderer.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (process crash) via crafted pkt_length and offlen values, which trigger an out-of-bounds access.
Weakness: CWE-190
Which versions are affected by CVE-2017-6355?
It affects 1 product.
Products include Freedesktop Virglrenderer.
How do I fix CVE-2017-6355?
Upgrade to a fixed version.
Is CVE-2017-6355 being exploited?
There is no known exploitation of CVE-2017-6355 in the wild and no public exploit code.
Sources
Also known as DEBIAN-CVE-2017-6355, GHSA-jw74-hhvm-7qcr.