# CVE-2007-2475: Privilege escalation in n/a

> Attackers can exploit the ADSCHEMA utility to grant themselves excess permissions on their own attributes, leading to privilege escalation.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2595-gj6q-jrrp

## What is CVE-2007-2475?

CVE-2007-2475 is a medium-severity vulnerability in n/a, published on 2 May 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the ADSCHEMA utility in Novell SecureLogin (NSL) 6 SP1 before 6.0.106 has unknown impact and remote attack vectors, related to granting "users excess permissions to their own attributes."

## Which versions are affected by CVE-2007-2475?

It affects 1 product.


Products: Novell Securelogin.

## How do I fix CVE-2007-2475?

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

## Is CVE-2007-2475 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2476](https://insights.sbomify.com/CVE-2007-2476/): Unspecified vulnerability in Novell SecureLogin (NSL) 6 SP1 before 6.0.106 has unknown impact and remote attack vectors, related to Active D (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2475 and fix it if it is affected.

What it is: CVE-2007-2475 is a medium-severity vulnerability in n/a, published on 2 May 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-2475 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-2007-2475/ (Markdown: https://insights.sbomify.com/CVE-2007-2475/index.md)
```

## Sources

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

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