{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-6629 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-6629 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-6629 is a high-severity path traversal vulnerability in n/a, published on 18 Dec 2006. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-6629 and fix it if it is affected.\n\nWhat it is: CVE-2006-6629 is a high-severity path traversal vulnerability in n/a, published on 18 Dec 2006. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2006-6629 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-2006-6629/ (Markdown: https://insights.sbomify.com/CVE-2006-6629/index.md)","id":"CVE-2006-6629","markdown":"https://insights.sbomify.com/CVE-2006-6629/index.md","name":"CVE-2006-6629","record":{"aliases":["GHSA-7qq7-gh46-3q87"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WeBWorK PG Language","requires_auth":"low_privilege","summary":"Attackers can load arbitrary macro files via insufficiently restrictive regex, potentially leading to code execution in WeBWorK.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"program_generation_language","vendor":"webwork"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"lib/WeBWorK/PG/Translator.pm in WeBWorK Program Generation (PG) Language before 2.3.1 uses an insufficiently restrictive regular expression to determine valid macro filenames, which allows attackers to load arbitrary macro files whose names contain the strings (1) dangerousMacros.pl, (2) PG.pl, or (3) IO.pl.","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":"Path traversal in n/a","id":"CVE-2006-6629","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2006"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in n/a","id":"CVE-2006-6630"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2006-6628"},"products":["n/a"],"published":"2006-12-18","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Attackers can load arbitrary macro files via insufficiently restrictive regex, potentially leading to code execution in WeBWorK.","url":"https://insights.sbomify.com/CVE-2006-6629/"}