# CVE-2003-1575: Auth bypass in n/a

> Local users can bypass file permissions on VxFS filesystems in Sun Solaris due to improper ACL inheritance, requiring a vendor patch.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 28 Jan 2010
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-598h-cgm6-2m38

## What is CVE-2003-1575?

CVE-2003-1575 is a medium-severity authentication bypass vulnerability in n/a, published on 28 Jan 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

VERITAS File System (VxFS) 3.3.3, 3.4, and 3.5 before MP1 Rolling Patch 02 for Sun Solaris 2.5.1 through 9 does not properly implement inheritance of default ACLs in certain circumstances related to the characteristics of a directory inode, which allows local users to bypass intended file permissions by accessing a file on a VxFS filesystem.

Weakness: CWE-264

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

It affects 1 product.


Products: Symantec Vxfs.

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

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

## Is CVE-2003-1575 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2003-1575 is a medium-severity authentication bypass vulnerability in n/a, published on 28 Jan 2010. 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-2003-1575 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-2003-1575/ (Markdown: https://insights.sbomify.com/CVE-2003-1575/index.md)
```

## Sources

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

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