# CVE-2005-1638: Cross-site scripting in n/a

> Remote attackers can bypass XSS protections in applications using SafeHTML by exploiting improper quote handling in attribute values.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 May 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-h32q-7jfw-fq6v

## What is CVE-2005-1638?

CVE-2005-1638 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 May 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The _writeAttrs function in SafeHTML before 1.3.2 does not properly handle quotes in attribute values, which could allow remote attackers to exploit cross-site scripting (XSS) vulnerabilities in applications that rely on SafeHTML for protection.

## Which versions are affected by CVE-2005-1638?

It affects 1 product.


Products: Pixel-Apes Group Safehtml.

## How do I fix CVE-2005-1638?

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

## Is CVE-2005-1638 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-0648](https://insights.sbomify.com/CVE-2005-0648/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2005-0649](https://insights.sbomify.com/CVE-2005-0649/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-1638 and fix it if it is affected.

What it is: CVE-2005-1638 is a medium-severity cross-site scripting vulnerability in n/a, published on 17 May 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-1638 in the wild and no public exploit code.

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-2005-1638/ (Markdown: https://insights.sbomify.com/CVE-2005-1638/index.md)
```

## Sources

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

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