# CVE-2005-3360: Privilege escalation in n/a

> Local attackers can escalate privileges and cause denial of service by modifying critical files due to insecure default ACLs in Trend Micro PC-Cillin.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q6c8-5hhp-w6rv

## What is CVE-2005-3360?

CVE-2005-3360 is a high-severity vulnerability in n/a, published on 14 Dec 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The installation of Trend Micro PC-Cillin Internet Security 2005 12.00 build 1244, and probably previous versions, uses insecure default ACLs, which allows local users to cause a denial of service (disabled service) and gain system privileges by modifying or moving critical program files.

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

It affects 1 product.


Products: Trend Micro Pc-Cillin 2005.

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

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

## Is CVE-2005-3360 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3360 is a high-severity vulnerability in n/a, published on 14 Dec 2005. 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-2005-3360 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-3360/ (Markdown: https://insights.sbomify.com/CVE-2005-3360/index.md)
```

## Sources

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

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