Skip to content
This page tracks the Debian fix status. The vulnerability itself is described on the main CVE page. View CVE-2019-19882 →
Unrated

Vulnerability in shadow

DEBIAN-CVE-2019-19882 First seen on SecPulse

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-2019-19882 has been found in shadow.
Successful exploitation can lead to full system takeover.
What to do: upgrade shadow to 1:4.8.1-1 or later.
If unsure, ask your IT team or search "shadow DEBIAN-CVE-2019-19882" on the vendor's site.

DEBIAN-CVE-2019-19882 (shadow)
Attack vector: local / no user interaction
Patched: 1:4.8.1-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.

What is the problem

A vulnerability (unclassified) exists in shadow.

Affected scope

Check the vendor advisory for the affected versions of shadow.

Severity

Severity: ?. Successful exploitation can lead to full system takeover.

How to fix

Update to 1:4.8.1-1.

Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'shadow' . 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. 1
    Identify exposureidentify
    grep -r 'shadow' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で shadow を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patchpatch
    Upgrade shadow to 1:4.8.1-1

    ステージング環境で 1:4.8.1-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verificationverify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

EcosystemPackageAffectedFixed
Debian:12 shadow
< 1:4.8.1-1
1:4.8.1-1
Debian:13 shadow
< 1:4.8.1-1
1:4.8.1-1
Debian:14 shadow
< 1:4.8.1-1
1:4.8.1-1
Original description The description as published by the source.

shadow 4.8, in certain circumstances affecting at least Gentoo, Arch Linux, and Void Linux, allows local users to obtain root access because setuid programs are misconfigured. Specifically, this affects shadow 4.8 when compiled using --with-libpam but without explicitly passing --disable-account-tools-setuid, and without a PAM configuration suitable for use with setuid account management tools. This combination leads to account management tools (groupadd, groupdel, groupmod, useradd, userdel, usermod) that can easily be used by unprivileged local users to escalate privileges to root in multiple ways. This issue became much more relevant in approximately December 2019 when an unrelated bug was fixed (i.e., the chmod calls to suidusbins were fixed in the upstream Makefile which is now included in the release version 4.8).

Source: OSV.dev (Open Source Vulnerabilities) OSV

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details