# CVE-2002-2323: Missing authorization in n/a

> Attackers can bypass access restrictions on files restored from backup due to improper ACL handling in Sun PC NetLink.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Oct 2007
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5888-494v-35jq

## What is CVE-2002-2323?

CVE-2002-2323 is a high-severity missing authorization vulnerability in n/a, published on 26 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sun PC NetLink 1.0 through 1.2 does not properly set the access control list (ACL) for files and directories that use symbolic links and have been restored from backup, which could allow local or remote attackers to bypass intended access restrictions.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-281 (Improper Preservation of Permissions)

## Which versions are affected by CVE-2002-2323?

It affects 1 product.


Products: Sun Solaris Pc Netlink.

## How do I fix CVE-2002-2323?

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

## Is CVE-2002-2323 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-4552](https://insights.sbomify.com/CVE-2005-4552/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-2323 and fix it if it is affected.

What it is: CVE-2002-2323 is a high-severity missing authorization vulnerability in n/a, published on 26 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-2323 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-2002-2323/ (Markdown: https://insights.sbomify.com/CVE-2002-2323/index.md)
```

## Sources

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

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