{"answers":{"affected":"3 open source packages ship an affected version, including slixmpp. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-1000021 in the wild and no public exploit code.","fix":"Upgrade slixmpp to 1.4.2 or later.","what":"CVE-2019-1000021 is a high-severity missing authorization vulnerability in n/a, published on 4 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-1000021 and fix it if it is affected.\n\nWhat it is: CVE-2019-1000021 is a high-severity missing authorization vulnerability in n/a, published on 4 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-1000021 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- slixmpp (PyPI): affected all versions; fixed in 1.4.2\n- slixmpp (PyPI): affected all versions; fixed in 1.4.2\n- slixmpp (PyPI): affected all versions; fixed in 1.4.2\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-1000021/ (Markdown: https://insights.sbomify.com/CVE-2019-1000021/index.md)","id":"CVE-2019-1000021","markdown":"https://insights.sbomify.com/CVE-2019-1000021/index.md","name":"CVE-2019-1000021","record":{"aliases":["DEBIAN-CVE-2019-1000021","GHSA-4g62-mfwx-4q48","PYSEC-2019-121","UBUNTU-CVE-2019-1000021","openSUSE-SU-2019:0163-1","openSUSE-SU-2019:0169-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"XMPP library","requires_auth":"none","summary":"An incorrect access control in slixmpp allows contacts to view private data if the user publishes to a PEP node without explicit privacy configuration.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"slixmpp","vendor":"slixmpp_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[],"description":"slixmpp version before commit 7cd73b594e8122dddf847953fcfc85ab4d316416 contains an incorrect Access Control vulnerability in XEP-0223 plugin (Persistent Storage of Private Data via PubSub) options profile, used for the configuration of default access model that can result in all of the contacts of the victim can see private data having been published to a PEP node. This attack appears to be exploitable if the user of this library publishes any private data on PEP, the node isn't configured to be private. This vulnerability appears to have been fixed in commit 7cd73b594e8122dddf847953fcfc85ab4d316416 which is included in slixmpp 1.4.2.","ecosystems":["PyPI","SUSE:Package Hub 15"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"slixmpp Incorrect Access Control","id":"CVE-2019-1000021","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"missing_authorization","year":"2019"},"n_packages":4,"n_references":4,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2019-1000022"},"packages":[{"ecosystem":"PyPI","fixed":["1.4.2"],"introduced":["0"],"last_affected":[],"package":"slixmpp","purl":null,"source":"GHSA-4g62-mfwx-4q48"},{"ecosystem":"PyPI","fixed":["1.4.2"],"introduced":["0"],"last_affected":[],"package":"slixmpp","purl":"pkg:pypi/slixmpp","source":"GHSA-4g62-mfwx-4q48"},{"ecosystem":"PyPI","fixed":["1.4.2"],"introduced":["0"],"last_affected":[],"package":"slixmpp","purl":"pkg:pypi/slixmpp","source":"PYSEC-2019-121"},{"ecosystem":"SUSE:Package Hub 15","fixed":["1.3.0-bp150.3.3.1"],"introduced":["0"],"last_affected":[],"package":"python-slixmpp","purl":"pkg:rpm/suse/python-slixmpp\u0026distro=SUSE%20Package%20Hub%2015","source":"openSUSE-SU-2019:0169-1"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2019-1000020"},"products":["n/a"],"published":"2019-02-04","related":[{"cvss_score":7.5,"headline":"Slixmpp lacks SSL Certificate hostname validation in XMLStream","id":"CVE-2022-45197","kev_date_added":null,"published":"2022-12-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An incorrect access control in slixmpp allows contacts to view private data if the user publishes to a PEP node without explicit privacy configuration.","url":"https://insights.sbomify.com/CVE-2019-1000021/"}