{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-18958 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-18958 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-18958 is a high-severity vulnerability in n/a, published on 21 Nov 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-18958 and fix it if it is affected.\n\nWhat it is: CVE-2019-18958 is a high-severity vulnerability in n/a, published on 21 Nov 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-18958 in the wild and no public exploit code.\n\nAffected product: n/a. 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-18958/ (Markdown: https://insights.sbomify.com/CVE-2019-18958/index.md)","id":"CVE-2019-18958","markdown":"https://insights.sbomify.com/CVE-2019-18958/index.md","name":"CVE-2019-18958","record":{"aliases":["GHSA-j395-6955-mv56"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PDF reader","requires_auth":"low_privilege","summary":"Nitro Pro creates a debug log file that can be edited and executed, potentially allowing arbitrary code execution if the file is manipulated.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nitro_pro","vendor":"gonitro"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"Nitro Pro before 13.2 creates a debug.log file in the directory where a .pdf file is located, if the .pdf document was produced by an OCR operation on the JPEG output of a scanner. Reportedly, this can have a security risk if debug.log is later edited and then executed.","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":"Other in n/a","id":"CVE-2019-18958","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-18960"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-18957"},"products":["n/a"],"published":"2019-11-21","related":[{"cvss_score":8.8,"headline":"Use after free in Nitro Pro","id":"CVE-2021-21796","kev_date_added":null,"published":"2021-10-18"},{"cvss_score":8.8,"headline":"Use after free in Nitro Pro","id":"CVE-2021-21797","kev_date_added":null,"published":"2021-10-18"},{"cvss_score":8.8,"headline":"Use after free in Nitro Pro","id":"CVE-2021-21798","kev_date_added":null,"published":"2021-09-15"},{"cvss_score":8.8,"headline":"Memory corruption in Nitro Pro","id":"CVE-2020-6112","kev_date_added":null,"published":"2020-09-17"},{"cvss_score":8.8,"headline":"Integer overflow in Nitro Pro","id":"CVE-2020-6113","kev_date_added":null,"published":"2020-09-17"},{"cvss_score":8.8,"headline":"Use after free in Nitro Pro","id":"CVE-2020-6115","kev_date_added":null,"published":"2020-09-17"},{"cvss_score":8.8,"headline":"Memory corruption in Nitro Pro","id":"CVE-2020-6116","kev_date_added":null,"published":"2020-09-17"}],"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-05","vendors":["n/a"]},"summary":"Nitro Pro creates a debug log file that can be edited and executed, potentially allowing arbitrary code execution if the file is manipulated.","url":"https://insights.sbomify.com/CVE-2019-18958/"}