# CVE-2003-1419: Netscape 7.0 allows remote attackers to cause a denial of service (crash) via a web page with an invalid regular expression argument to the


- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-8fpc-7gj8-q327

## What is CVE-2003-1419?

CVE-2003-1419 is a medium-severity vulnerability in n/a, published on 20 Oct 2007. 

### Official description

Netscape 7.0 allows remote attackers to cause a denial of service (crash) via a web page with an invalid regular expression argument to the JavaScript reformatDate function.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2003-1419?

It affects 1 product.


Products: Netscape Navigator.

## How do I fix CVE-2003-1419?

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

## Is CVE-2003-1419 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1419 exists.

Public exploit code:

- Netscape 7.0 - JavaScript Regular Expression Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-1160](https://insights.sbomify.com/CVE-2004-1160/): Other in n/a (high 7.5)
- [CVE-2003-0553](https://insights.sbomify.com/CVE-2003-0553/): Memory corruption in n/a (high 7.5)
- [CVE-1999-0142](https://insights.sbomify.com/CVE-1999-0142/): Security feature bypass in n/a (high 7.5)
- [CVE-2003-1560](https://insights.sbomify.com/CVE-2003-1560/): Information disclosure in n/a (medium 5.0)
- [CVE-2004-0528](https://insights.sbomify.com/CVE-2004-0528/): Other in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-1419 and fix it if it is affected.

What it is: CVE-2003-1419 is a medium-severity vulnerability in n/a, published on 20 Oct 2007. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-1419 exists.

Affected product: n/a. 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-2003-1419/ (Markdown: https://insights.sbomify.com/CVE-2003-1419/index.md)
```

## Sources

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

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