{"answers":{"affected":"2 open source packages ship an affected version, including jpv. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19507 in the wild and no public exploit code.","fix":"Upgrade jpv to 2.1.1 or later.","what":"CVE-2019-19507 is a medium-severity vulnerability in n/a, published on 2 Dec 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-19507 and fix it if it is affected.\n\nWhat it is: CVE-2019-19507 is a medium-severity vulnerability in n/a, published on 2 Dec 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-19507 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- jpv (npm): affected all versions; fixed in 2.1.1\n- jpv (npm): affected all versions; fixed in 2.1.1\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-19507/ (Markdown: https://insights.sbomify.com/CVE-2019-19507/index.md)","id":"CVE-2019-19507","markdown":"https://insights.sbomify.com/CVE-2019-19507/index.md","name":"CVE-2019-19507","record":{"aliases":["GHSA-rh46-3fgc-mvrf"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript validation library","requires_auth":"none","summary":"Attackers can bypass type validation in the jpv library by overwriting internal attributes, allowing crafted payloads to evade security checks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"json_pattern_validator","vendor":"json_pattern_validator_project"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"In jpv (aka Json Pattern Validator) before 2.1.1, compareCommon() can be bypassed because certain internal attributes can be overwritten via a conflicting name, as demonstrated by 'constructor': {'name':'Array'}. This affects validate(). Hence, a crafted payload can overwrite this builtin attribute to manipulate the type detection result.","ecosystems":["npm"],"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":"Validation bypass is possible in Json Pattern Validator","id":"CVE-2019-19507","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2019-19509"},"packages":[{"ecosystem":"npm","fixed":["2.1.1"],"introduced":["0"],"last_affected":[],"package":"jpv","purl":null,"source":"GHSA-rh46-3fgc-mvrf"},{"ecosystem":"npm","fixed":["2.1.1"],"introduced":["0"],"last_affected":[],"package":"jpv","purl":"pkg:npm/jpv","source":"GHSA-rh46-3fgc-mvrf"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2019-19506"},"products":["n/a"],"published":"2019-12-02","related":[{"cvss_score":9.8,"headline":"Validation bypass in jpv","id":"CVE-2020-17479","kev_date_added":null,"published":"2020-08-10"}],"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":"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":"Attackers can bypass type validation in the jpv library by overwriting internal attributes, allowing crafted payloads to evade security checks.","url":"https://insights.sbomify.com/CVE-2019-19507/"}