# CVE-2015-1974: Security feature bypass in n/a

> Authenticated users can bypass command restrictions in the IBM Tivoli Security Directory Server web administration tool.

- **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:** 28 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f3p2-j336-wh42

## What is CVE-2015-1974?

CVE-2015-1974 is a medium-severity vulnerability in n/a, published on 28 Jun 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The web administration tool in IBM Tivoli Security Directory Server 6.0 before iFix 75, 6.1 before iFix 68, 6.2 before iFix 44, 6.3 before iFix 37, 6.3.1 before iFix 11, and 6.4 before iFix 2 allows remote authenticated users to bypass intended command restrictions via unspecified vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2015-1974?

It affects 1 product.


Products: Ibm Tivoli Directory Server.

## How do I fix CVE-2015-1974?

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

## Is CVE-2015-1974 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-1206](https://insights.sbomify.com/CVE-2011-1206/): Memory corruption in n/a (critical 10.0)
- [CVE-2015-1975](https://insights.sbomify.com/CVE-2015-1975/): Command injection in n/a (high 7.8)
- [CVE-2009-3089](https://insights.sbomify.com/CVE-2009-3089/): Null dereference in n/a (high 7.8)
- [CVE-2009-3088](https://insights.sbomify.com/CVE-2009-3088/): Memory corruption in n/a (high 7.5)
- [CVE-2007-6742](https://insights.sbomify.com/CVE-2007-6742/): Denial of service in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1974 and fix it if it is affected.

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

## Sources

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

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