{"answers":{"affected":"2 open source packages ship an affected version, including fast-xml-parser.","exploited":"There is no known exploitation of GHSA-gpv5-7x3g-ghjv in the wild and no public exploit code.","fix":"Upgrade fast-xml-parser to 4.2.5 or later.","what":"GHSA-gpv5-7x3g-ghjv is a vulnerability in fast-xml-parser, published on 15 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-gpv5-7x3g-ghjv and fix it if it is affected.\n\nWhat it is: GHSA-gpv5-7x3g-ghjv is a vulnerability in fast-xml-parser, published on 15 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-gpv5-7x3g-ghjv in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- fast-xml-parser (npm): affected from 4.2.4; fixed in 4.2.5\n- fast-xml-parser (npm): affected from 4.2.4; fixed in 4.2.5\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/GHSA-gpv5-7x3g-ghjv/ (Markdown: https://insights.sbomify.com/GHSA-gpv5-7x3g-ghjv/index.md)","id":"GHSA-gpv5-7x3g-ghjv","markdown":"https://insights.sbomify.com/GHSA-gpv5-7x3g-ghjv/index.md","name":"GHSA-gpv5-7x3g-ghjv","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript XML parser","requires_auth":"none","summary":"An attacker can exploit insufficient entity name validation in fast-xml-parser to potentially trigger XML External Entity attacks, leading to data exposure or service disruption.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Summary\nThis is a comment on https://github.com/NaturalIntelligence/fast-xml-parser/security/advisories/GHSA-6w63-h3fj-q4vw and the patches fixing it.\n\n### Details\nThe code which validates a name calls the validator:\nhttps://github.com/NaturalIntelligence/fast-xml-parser/blob/ecf6016f9b48aec1a921e673158be0773d07283e/src/xmlparser/DocTypeReader.js#L145-L153\nThis checks for the presence of an invalid character.  Such an approach is always risky, as it is so easy to forget to include an invalid character in the list.  A safer approach is to validate entity names against the XML specification: https://www.w3.org/TR/xml11/#sec-common-syn - an ENTITY name is a Name:\n\n```\n[4]   NameStartChar ::= \":\" | [A-Z] | \"_\" | [a-z] | [#xC0-#xD6] | [#xD8-#xF6] | [#xF8-#x2FF] | [#x370-#x37D] |\n                        [#x37F-#x1FFF] | [#x200C-#x200D] | [#x2070-#x218F] | [#x2C00-#x2FEF] | [#x3001-#xD7FF] |\n                        [#xF900-#xFDCF] | [#xFDF0-#xFFFD] | [#x10000-#xEFFFF]\n[4a]  NameChar ::= NameStartChar | \"-\" | \".\" | [0-9] | #xB7 | [#x0300-#x036F] | [#x203F-#x2040]\n[5]   Name ::= NameStartChar (NameChar)*\n```\n\nso the safest way to validate an entity name is to build a regex to represent this expression and check whether the name given matches the regex.  (Something along the lines of `/^[name start char class][name char class]*$/`.)  There's probably a nice way to simplify the explicit list rather than typing it out verbatim using Unicode character properties, but I don't know enough to do so.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"fast-xml-parser regex vulnerability patch could be improved from a safety perspective","id":"GHSA-gpv5-7x3g-ghjv","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"xxe","year":"2023"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["4.2.5"],"introduced":["4.2.4"],"last_affected":[],"package":"fast-xml-parser","purl":null,"source":"GHSA-gpv5-7x3g-ghjv"},{"ecosystem":"npm","fixed":["4.2.5"],"introduced":["4.2.4"],"last_affected":[],"package":"fast-xml-parser","purl":"pkg:npm/fast-xml-parser","source":"GHSA-gpv5-7x3g-ghjv"}],"products":null,"published":"2023-06-15","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An attacker can exploit insufficient entity name validation in fast-xml-parser to potentially trigger XML External Entity attacks, leading to data exposure or service disruption.","url":"https://insights.sbomify.com/GHSA-gpv5-7x3g-ghjv/"}