{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2015-3335 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-3335 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-3335 is a high-severity vulnerability in Google Chrome, published on 19 Apr 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2015-3335 and fix it if it is affected.\n\nWhat it is: CVE-2015-3335 is a high-severity vulnerability in Google Chrome, published on 19 Apr 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2015-3335 in the wild and no public exploit code.\n\nAffected product: Google Chrome. 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-2015-3335/ (Markdown: https://insights.sbomify.com/CVE-2015-3335/index.md)","id":"CVE-2015-3335","markdown":"https://insights.sbomify.com/CVE-2015-3335/index.md","name":"CVE-2015-3335","record":{"aliases":["GHSA-4rcp-p5x7-vvjf"],"analysis":{"component_type":"browser","fix_type":"upgrade","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Google Chrome","requires_auth":"none","summary":"Missing resource limits in Chrome's NaCl sandbox allow attackers to bypass security controls, potentially facilitating row-hammer attacks or other impacts.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"chrome","vendor":"google"},{"product":"opensuse","vendor":"opensuse"}],"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":[{"id":"CWE-264","name":null}],"description":"The NaClSandbox::InitializeLayerTwoSandbox function in components/nacl/loader/sandbox_linux/nacl_sandbox_linux.cc in Google Chrome before 42.0.2311.90 does not have RLIMIT_AS and RLIMIT_DATA limits for Native Client (aka NaCl) processes, which might make it easier for remote attackers to conduct row-hammer attacks or have unspecified other impact by leveraging the ability to run a crafted program in the NaCl sandbox.","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":"Security feature bypass in n/a","id":"CVE-2015-3335","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:chrome","products":["google:chrome","opensuse:opensuse"],"type":"security_feature_bypass","year":"2015"},"n_packages":0,"n_references":4,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2015-3336"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2015-3334"},"products":["n/a"],"published":"2015-04-19","related":[{"cvss_score":9.6,"headline":"Google Chromium GPU Heap Buffer Overflow","id":"CVE-2022-4135","kev_date_added":"2022-11-28","published":"2022-11-25"},{"cvss_score":9.6,"headline":"Google Chrome Use-After-Free","id":"CVE-2020-16017","kev_date_added":"2021-11-03","published":"2021-01-08"},{"cvss_score":9.6,"headline":"Google Chrome for Android UI Heap Buffer Overflow","id":"CVE-2020-16010","kev_date_added":"2021-11-03","published":"2020-11-03"},{"cvss_score":8.8,"headline":"Google Chromium V8 Out of Bounds Write","id":"CVE-2026-87491","kev_date_added":"2026-09-09","published":"2026-09-09"},{"cvss_score":8.8,"headline":"Google Chromium V8 Type Confusion","id":"CVE-2026-85046","kev_date_added":"2026-09-04","published":"2026-09-03"},{"cvss_score":8.8,"headline":"Google Chromium V8 Out-of-Bounds Read and Write","id":"CVE-2026-11645","kev_date_added":"2026-06-09","published":"2026-06-08"},{"cvss_score":8.8,"headline":"Google Dawn Use-After-Free","id":"CVE-2026-5281","kev_date_added":"2026-04-01","published":"2026-04-01"}],"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-08-06","vendors":["n/a"]},"summary":"Missing resource limits in Chrome's NaCl sandbox allow attackers to bypass security controls, potentially facilitating row-hammer attacks or other impacts.","url":"https://insights.sbomify.com/CVE-2015-3335/"}