{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-0004 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-0004 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-0004 is a high-severity vulnerability in Juniper ATP, published on 15 Jan 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-0004 and fix it if it is affected.\n\nWhat it is: CVE-2019-0004 is a high-severity vulnerability in Juniper ATP, published on 15 Jan 2019. 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-0004 in the wild and no public exploit code.\n\nAffected product: Juniper ATP. 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-0004/ (Markdown: https://insights.sbomify.com/CVE-2019-0004/index.md)","id":"CVE-2019-0004","markdown":"https://insights.sbomify.com/CVE-2019-0004/index.md","name":"CVE-2019-0004","record":{"aliases":["GHSA-q664-xxjg-cm3g"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Juniper ATP","requires_auth":"low_privilege","summary":"Authenticated local users can read API and device keys from a world-readable log file, potentially allowing unauthorized access to critical WebUI operations.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"juniper","cpe":[{"product":"advanced_threat_prevention","vendor":"juniper"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"On Juniper ATP, the API key and the device key are logged in a file readable by authenticated local users. These keys are used for performing critical operations on the WebUI interface. This issue affects Juniper ATP 5.0 versions prior to 5.0.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Juniper ATP: API and device keys are logged in a world-readable permissions file","id":"CVE-2019-0004","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2019-0005"},"packages":[],"prev":{"headline":"Denial of service in Junos OS","id":"CVE-2019-0003"},"products":["Juniper ATP"],"published":"2019-01-15","related":[{"cvss_score":10,"headline":"Juniper ATP: Hard coded credentials used in Web Collector","id":"CVE-2019-0020","kev_date_added":null,"published":"2019-01-15"},{"cvss_score":10,"headline":"Hardcoded credentials in Juniper ATP","id":"CVE-2019-0022","kev_date_added":null,"published":"2019-01-15"},{"cvss_score":8.8,"headline":"Juniper ATP: Splunk credentials are in logged in clear text","id":"CVE-2019-0029","kev_date_added":null,"published":"2019-01-15"},{"cvss_score":7.1,"headline":"Juniper ATP: secret CLI inputs are logged to /var/log/syslog in clear text","id":"CVE-2019-0021","kev_date_added":null,"published":"2019-01-15"},{"cvss_score":5.4,"headline":"Juniper ATP: Persistent Cross-Site Scripting (XSS) vulnerability in file upload menu","id":"CVE-2019-0018","kev_date_added":null,"published":"2019-01-15"},{"cvss_score":5.4,"headline":"Juniper ATP: Persistent Cross-Site Scripting vulnerability in the Golden VM menu","id":"CVE-2019-0023","kev_date_added":null,"published":"2019-01-15"}],"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-09-16","vendors":["Juniper Networks"]},"summary":"Authenticated local users can read API and device keys from a world-readable log file, potentially allowing unauthorized access to critical WebUI operations.","url":"https://insights.sbomify.com/CVE-2019-0004/"}