# CVE-2008-3521: Race condition in n/a

> A local attacker can cause a denial of service in JasPer by exploiting a race condition in temporary file creation.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vjjh-7673-9x6q

## What is CVE-2008-3521?

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.

### Official 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.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2008-3521?

It affects 1 product.


Products: Jasper Project Jasper.

## How do I fix CVE-2008-3521?

No fix has been published for CVE-2008-3521 yet. Limit exposure of the affected software until one is available.

## Is CVE-2008-3521 being exploited?

There is no known exploitation of CVE-2008-3521 in the wild and no public exploit code.

## Other vulnerabilities in Jasper Project Jasper

- [CVE-2008-3522](https://insights.sbomify.com/CVE-2008-3522/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-3520](https://insights.sbomify.com/CVE-2008-3520/): Integer overflow in n/a (critical 9.3)
- [CVE-2015-8751](https://insights.sbomify.com/CVE-2015-8751/): Integer overflow in n/a (high 8.8)
- [CVE-2023-51257](https://insights.sbomify.com/CVE-2023-51257/): Memory corruption in n/a (high 7.8)
- [CVE-2016-8886](https://insights.sbomify.com/CVE-2016-8886/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3521 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2008-3521 in the wild and no public exploit code.

Affected product: Jasper Project Jasper. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2008-3521/ (Markdown: https://insights.sbomify.com/CVE-2008-3521/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2008-3521
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2008-3521
- OSV: https://osv.dev/vulnerability/CVE-2008-3521

---
From sbomify Insights: https://insights.sbomify.com/CVE-2008-3521/
Summaries are generated and may contain mistakes; the official description above is the record.