{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2019-13033 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2019-13033 is a low-severity vulnerability in Debian Debian Linux, published on 18 Jun 2020. 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-13033 and fix it if it is affected.\n\nWhat it is: CVE-2019-13033 is a low-severity vulnerability in Debian Debian Linux, published on 18 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-13033 in the wild and no public exploit code.\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-13033/ (Markdown: https://insights.sbomify.com/CVE-2019-13033/index.md)","id":"CVE-2019-13033","markdown":"https://insights.sbomify.com/CVE-2019-13033/index.md","name":"CVE-2019-13033","record":{"aliases":["DEBIAN-CVE-2019-13033","DLA-2253-1","GHSA-vxcg-qj63-4mp6","UBUNTU-CVE-2019-13033"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Lynis security auditing","requires_auth":"low_privilege","summary":"Attackers can obtain the license key from the process list during uploads, allowing unauthorized data submission to the central server.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lynis","vendor":"cisofy"},{"product":"debian_linux","vendor":"debian"},{"product":"fedora","vendor":"fedoraproject"}],"cvss":{"score":3.3,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"In CISOfy Lynis 2.x through 2.7.5, the license key can be obtained by looking at the process list when a data upload is being performed. This license can be used to upload data to a central Lynis server. Although no data can be extracted by knowing the license key, it may be possible to upload the data of additional scans.","ecosystems":[],"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":"Information disclosure in n/a","id":"CVE-2019-13033","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"debian:debian_linux","products":["debian:debian_linux","fedoraproject:fedora"],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":4,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2019-13035"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2019-13032"},"products":["n/a"],"published":"2020-06-18","related":[{"cvss_score":7.8,"headline":"Path traversal in n/a","id":"CVE-2017-8108","kev_date_added":null,"published":"2017-06-08"},{"cvss_score":4.2,"headline":"Race condition in n/a","id":"CVE-2020-13882","kev_date_added":null,"published":"2020-06-18"},{"cvss_score":3.3,"headline":"Path traversal in n/a","id":"CVE-2014-3982","kev_date_added":null,"published":"2014-06-08"},{"cvss_score":3.3,"headline":"Path traversal in n/a","id":"CVE-2014-3986","kev_date_added":null,"published":"2014-06-08"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can obtain the license key from the process list during uploads, allowing unauthorized data submission to the central server.","url":"https://insights.sbomify.com/CVE-2019-13033/"}