{"answers":{"affected":"It affects 4 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-3842 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2019-3842 is a medium-severity vulnerability in Debian Debian Linux, published on 9 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-3842 and fix it if it is affected.\n\nWhat it is: CVE-2019-3842 is a medium-severity vulnerability in Debian Debian Linux, published on 9 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-3842 exists.\n\nAffected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-3842/ (Markdown: https://insights.sbomify.com/CVE-2019-3842/index.md)","id":"CVE-2019-3842","markdown":"https://insights.sbomify.com/CVE-2019-3842/index.md","name":"CVE-2019-3842","record":{"aliases":["DEBIAN-CVE-2019-3842","DSA-4428-1","GHSA-c23j-qp89-q76c","UBUNTU-CVE-2019-3842","USN-3938-1"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"systemd PAM module","requires_auth":"low_privilege","summary":"Attackers can bypass polkit authorization checks by manipulating the XDG_SEAT environment variable in specific systemd configurations.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"debian_linux","vendor":"debian"},{"product":"fedora","vendor":"fedoraproject"},{"product":"enterprise_linux","vendor":"redhat"},{"product":"systemd","vendor":"systemd_project"}],"cvss":{"score":4.5,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"In systemd before v242-rc4, it was discovered that pam_systemd does not properly sanitize the environment before using the XDG_SEAT variable. It is possible for an attacker, in some particular configurations, to set a XDG_SEAT environment variable which allows for commands to be checked against polkit policies using the \"allow_active\" element rather than \"allow_any\".","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2019-04-23","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-04-23","kind":"exploitdb","ref":"46743","stars":null,"title":"systemd - Lack of Seat Verification in PAM Module Permits Spoofing Active Session to polkit"}],"tier":"weaponised"},"has_fix":true,"headline":"Security feature bypass in systemd","id":"CVE-2019-3842","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"debian:debian_linux","products":["debian:debian_linux","fedoraproject:fedora","redhat:enterprise_linux","systemd_project:systemd"],"type":"security_feature_bypass","year":"2019"},"n_packages":0,"n_references":8,"next":{"headline":"Privilege escalation in systemd","id":"CVE-2019-3843"},"packages":[],"prev":{"headline":"Security feature bypass in kubevirt/virt-cdi-importer","id":"CVE-2019-3841"},"products":["systemd"],"published":"2019-04-09","related":[{"cvss_score":10,"headline":"ProFTPD Improper Access Control","id":"CVE-2015-3306","kev_date_added":"2026-10-08","published":"2015-05-18"},{"cvss_score":9.9,"headline":"RoundCube Webmail Deserialization of Untrusted Data","id":"CVE-2025-49113","kev_date_added":"2026-02-20","published":"2025-06-02"},{"cvss_score":9.8,"headline":"GNU InetUtils Argument Injection","id":"CVE-2026-24061","kev_date_added":"2026-01-26","published":"2026-01-21"},{"cvss_score":9.8,"headline":"Linux Kernel Improper Check for Unusual or Exceptional Conditions","id":"CVE-2025-39682","kev_date_added":"2026-09-18","published":"2025-09-05"},{"cvss_score":9.8,"headline":"Mozilla Firefox Use-After-Free","id":"CVE-2024-9680","kev_date_added":"2024-10-15","published":"2024-10-09"},{"cvss_score":9.8,"headline":"RARLAB UnRAR Directory Traversal","id":"CVE-2022-30333","kev_date_added":"2022-08-09","published":"2022-05-09"},{"cvss_score":9.8,"headline":"Roundcube Webmail SQL Injection","id":"CVE-2021-44026","kev_date_added":"2023-06-22","published":"2021-11-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-09","vendors":["The systemd Project"]},"summary":"Attackers can bypass polkit authorization checks by manipulating the XDG_SEAT environment variable in specific systemd configurations.","url":"https://insights.sbomify.com/CVE-2019-3842/"}