{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.sling:org.apache.sling.jcr.contentloader. It affects 1 product.","exploited":"There is no known exploitation of CVE-2012-3353 in the wild and no public exploit code.","fix":"Upgrade org.apache.sling:org.apache.sling.jcr.contentloader to 2.1.6 or later.","what":"CVE-2012-3353 is a high-severity path traversal vulnerability in Apache Sling, published on 8 Jan 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-2012-3353 and fix it if it is affected.\n\nWhat it is: CVE-2012-3353 is a high-severity path traversal vulnerability in Apache Sling, published on 8 Jan 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-2012-3353 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.sling:org.apache.sling.jcr.contentloader (Maven): affected all versions; fixed in 2.1.6\n- org.apache.sling:org.apache.sling.jcr.contentloader (Maven): affected all versions; fixed in 2.1.6\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-2012-3353/ (Markdown: https://insights.sbomify.com/CVE-2012-3353/index.md)","id":"CVE-2012-3353","markdown":"https://insights.sbomify.com/CVE-2012-3353/index.md","name":"CVE-2012-3353","record":{"aliases":["GHSA-wjp3-4xcq-598p"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Sling JCR ContentLoader","requires_auth":"none","summary":"An attacker can import arbitrary local files into the content repository, leading to potential information disclosure.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"sling_jcr_contentloader","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-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The Apache Sling JCR ContentLoader 2.1.4 XmlReader used in the Sling JCR content loader module makes it possible to import arbitrary files in the content repository, including local files, causing potential information leaks. Users should upgrade to version 2.1.6 of the JCR ContentLoader","ecosystems":["Maven"],"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":"Apache Sling JCR ContentLoader XmlReader Arbitrary File Load","id":"CVE-2012-3353","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2012"},"n_packages":2,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2012-3354"},"packages":[{"ecosystem":"Maven","fixed":["2.1.6"],"introduced":["0"],"last_affected":[],"package":"org.apache.sling:org.apache.sling.jcr.contentloader","purl":null,"source":"GHSA-wjp3-4xcq-598p"},{"ecosystem":"Maven","fixed":["2.1.6"],"introduced":["0"],"last_affected":[],"package":"org.apache.sling:org.apache.sling.jcr.contentloader","purl":"pkg:maven/org.apache.sling/org.apache.sling.jcr.contentloader","source":"GHSA-wjp3-4xcq-598p"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2012-3351"},"products":["Apache Sling"],"published":"2018-01-08","related":[],"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-09-16","vendors":["Apache Software Foundation"]},"summary":"An attacker can import arbitrary local files into the content repository, leading to potential information disclosure.","url":"https://insights.sbomify.com/CVE-2012-3353/"}