# CVE-2003-1323: Privilege escalation in n/a

> Local users can escalate privileges to the mail group to read and modify files when Elm ME+ is setgid and the OS lacks POSIX saved ID support.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 30 Mar 2007
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-9cmq-xm5p-pqc3

## What is CVE-2003-1323?

CVE-2003-1323 is a medium-severity vulnerability in n/a, published on 30 Mar 2007. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Elm ME+ 2.4 before PL109S, when installed setgid mail and the operating system lacks POSIX saved ID support, allows local users to read and modify certain files with the privileges of the mail group via unspecified vectors.

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

It affects 1 product.


Products: Elm Development Group Elm.

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

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

## Is CVE-2003-1323 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2665](https://insights.sbomify.com/CVE-2005-2665/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0966](https://insights.sbomify.com/CVE-2003-0966/): Memory corruption in n/a (high 7.5)
- [CVE-2001-1174](https://insights.sbomify.com/CVE-2001-1174/): Memory corruption in n/a (high 7.5)
- [CVE-1999-1334](https://insights.sbomify.com/CVE-1999-1334/): Memory corruption in n/a (high 7.5)
- [CVE-1999-1184](https://insights.sbomify.com/CVE-1999-1184/): Memory corruption in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-1323 is a medium-severity vulnerability in n/a, published on 30 Mar 2007. 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-1323 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-1323/ (Markdown: https://insights.sbomify.com/CVE-2003-1323/index.md)
```

## Sources

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

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