# CVE-2005-1331: Code injection in n/a

> Remote attackers can trick users into executing malicious code by exploiting AppleScript Editor's improper display of applescript URIs.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **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:** 4 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6qxm-23hq-hvpc

## What is CVE-2005-1331?

CVE-2005-1331 is a medium-severity code injection vulnerability in Apple Mac Os X, published on 4 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 AppleScript Editor in Mac OS X 10.3.9 does not properly display script code for an applescript: URI, which can result in code that is different than the actual code that would be run, which could allow remote attackers to trick users into executing malicious code via certain URI characters such as NULL, control characters, and homographs.

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

It affects 3 products.


Products: Apple Applescript, Apple Mac Os X, Apple Mac Os X Server.

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

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

## Is CVE-2005-1331 being exploited?

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

## Other vulnerabilities in Apple Mac Os X

- [CVE-2011-0173](https://insights.sbomify.com/CVE-2011-0173/): Other in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1331 is a medium-severity code injection vulnerability in Apple Mac Os X, published on 4 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-1331 in the wild and no public exploit code.

Affected product: Apple Mac Os X. 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-1331/ (Markdown: https://insights.sbomify.com/CVE-2005-1331/index.md)
```

## Sources

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

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