Vulnerability in wayland
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as DEBIAN-CVE-2021-3782 has been found in wayland.
Risk of unauthorized operations or information disclosure.
What to do: upgrade wayland to 1.21.0-1 or later.
If unsure, ask your IT team or search "wayland DEBIAN-CVE-2021-3782" on the vendor's site.
DEBIAN-CVE-2021-3782 (wayland)
Attack vector: local / no user interaction
Patched: 1.21.0-1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in wayland.
Check the vendor advisory for the affected versions of wayland.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.21.0-1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'wayland' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'wayland' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
waylandを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade wayland to 1.21.0-1ステージング環境で 1.21.0-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Debian:12 | wayland |
< 1.21.0-1 |
1.21.0-1 |
| Debian:13 | wayland |
< 1.21.0-1 |
1.21.0-1 |
| Debian:14 | wayland |
< 1.21.0-1 |
1.21.0-1 |
Original description The description as published by the source.
An internal reference count is held on the buffer pool, incremented every time a new buffer is created from the pool. The reference count is maintained as an int; on LP64 systems this can cause the reference count to overflow if the client creates a large number of wl_shm buffer objects, or if it can coerce the server to create a large number of external references to the buffer storage. With the reference count overflowing, a use-after-free can be constructed on the wl_shm_pool tracking structure, where values may be incremented or decremented; it may also be possible to construct a limited oracle to leak 4 bytes of server-side memory to the attacking client at a time.
Source: OSV.dev (Open Source Vulnerabilities) OSV
References
- advisory security-tracker.debian.org