{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1299 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-1299 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-1299 is a high-severity path traversal vulnerability in Apache Allura, published on 6 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-1299 and fix it if it is affected.\n\nWhat it is: CVE-2018-1299 is a high-severity path traversal vulnerability in Apache Allura, published on 6 Feb 2018. 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-2018-1299 in the wild and no public exploit code.\n\nAffected product: Apache Allura. 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-2018-1299/ (Markdown: https://insights.sbomify.com/CVE-2018-1299/index.md)","id":"CVE-2018-1299","markdown":"https://insights.sbomify.com/CVE-2018-1299/index.md","name":"CVE-2018-1299","record":{"aliases":["GHSA-693w-mp32-8pwq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Apache Allura","requires_auth":"none","summary":"Unauthenticated attackers can retrieve arbitrary files from Apache Allura when deployed with vulnerable web servers like gunicorn.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"allura","vendor":"apache"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"In Apache Allura before 1.8.0, unauthenticated attackers may retrieve arbitrary files through the Allura web application. Some webservers used with Allura, such as Nginx, Apache/mod_wsgi or paster may prevent the attack from succeeding. Others, such as gunicorn do not prevent it and leave Allura vulnerable.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Path traversal in Apache Allura","id":"CVE-2018-1299","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2018-1300"},"packages":[],"prev":{"headline":"Moderate severity vulnerability that affects org.apache.qpid:apache-qpid-broker-j","id":"CVE-2018-1298"},"products":["Apache Allura"],"published":"2018-02-06","related":[{"cvss_score":9.8,"headline":"Apache Allura: Git command injection","id":"CVE-2026-73240","kev_date_added":null,"published":"2026-08-12"},{"cvss_score":9.1,"headline":"Apache Allura: Server-side request forgery","id":"CVE-2026-69223","kev_date_added":null,"published":"2026-08-11"},{"cvss_score":7.5,"headline":"Apache Allura: sensitive information exposure via DNS rebinding","id":"CVE-2024-36471","kev_date_added":null,"published":"2024-06-10"},{"cvss_score":6.5,"headline":"Apache Allura: Missing permission checks IDOR","id":"CVE-2026-73239","kev_date_added":null,"published":"2026-08-12"},{"cvss_score":6.1,"headline":"Apache Allura: XSS in markdown pipeline","id":"CVE-2026-73237","kev_date_added":null,"published":"2026-08-12"},{"cvss_score":6.1,"headline":"Apache Allura: XSS in code display","id":"CVE-2026-73238","kev_date_added":null,"published":"2026-08-12"}],"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":["Apache Software Foundation"]},"summary":"Unauthenticated attackers can retrieve arbitrary files from Apache Allura when deployed with vulnerable web servers like gunicorn.","url":"https://insights.sbomify.com/CVE-2018-1299/"}