{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2008-3521 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2008-3521 yet. Limit exposure of the affected software until one is available.","what":"CVE-2008-3521 is a high-severity vulnerability in Jasper Project Jasper, published on 2 Oct 2008. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2008-3521 and fix it if it is affected.\n\nWhat it is: CVE-2008-3521 is a high-severity vulnerability in Jasper Project Jasper, published on 2 Oct 2008. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2008-3521 in the wild and no public exploit code.\n\nAffected product: Jasper Project Jasper. 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-2008-3521/ (Markdown: https://insights.sbomify.com/CVE-2008-3521/index.md)","id":"CVE-2008-3521","markdown":"https://insights.sbomify.com/CVE-2008-3521/index.md","name":"CVE-2008-3521","record":{"aliases":["GHSA-vjjh-7673-9x6q"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"JasPer image library","requires_auth":"none","summary":"A local attacker can cause a denial of service in JasPer by exploiting a race condition in temporary file creation.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"jasper","vendor":"jasper_project"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"AV:L/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"Race condition in the jas_stream_tmpfile function in libjasper/base/jas_stream.c in JasPer 1.900.1 allows local users to cause a denial of service (program exit) by creating the appropriate tmp.XXXXXXXXXX temporary file, which causes Jasper to exit.  NOTE: this was originally reported as a symlink issue, but this was incorrect.  NOTE: some vendors dispute the severity of this issue, but it satisfies CVE's requirements for inclusion.","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":"Race condition in n/a","id":"CVE-2008-3521","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"jasper_project:jasper","products":["jasper_project:jasper"],"type":"race_condition","year":"2008"},"n_packages":0,"n_references":9,"next":{"headline":"Memory corruption in n/a","id":"CVE-2008-3522"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2008-3520"},"products":["n/a"],"published":"2008-10-02","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2008-3522","kev_date_added":null,"published":"2008-10-02"},{"cvss_score":9.3,"headline":"Integer overflow in n/a","id":"CVE-2008-3520","kev_date_added":null,"published":"2008-10-02"},{"cvss_score":8.8,"headline":"Integer overflow in n/a","id":"CVE-2015-8751","kev_date_added":null,"published":"2020-02-17"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2023-51257","kev_date_added":null,"published":"2024-01-16"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2016-8886","kev_date_added":null,"published":"2017-03-23"},{"cvss_score":7.8,"headline":"Integer overflow in n/a","id":"CVE-2016-9387","kev_date_added":null,"published":"2017-03-23"},{"cvss_score":7.8,"headline":"Integer overflow in n/a","id":"CVE-2016-10249","kev_date_added":null,"published":"2017-03-15"}],"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-07","vendors":["n/a"]},"summary":"A local attacker can cause a denial of service in JasPer by exploiting a race condition in temporary file creation.","url":"https://insights.sbomify.com/CVE-2008-3521/"}