# CVE-2015-0146: Missing authorization in n/a

> Local users can bypass document-access restrictions in IBM Content Collector to obtain sensitive information via crafted search queries.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **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:** 18 Mar 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3hrm-jr5c-jm96

## What is CVE-2015-0146?

CVE-2015-0146 is a low-severity missing authorization vulnerability in n/a, published on 18 Mar 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Content Collector for Email 3.0 before 3.0.0.6-IBM-ICC-Server-IF001 and 4.0 before 4.0.0.3-IBM-ICC-Server-IF001 does not properly handle an unspecified query operator during searches of IBM FileNet P8 systems with IBM Content Search Services, which allows local users to bypass intended document-access restrictions and obtain sensitive information via a crafted search query.

Weakness: CWE-264

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

It affects 1 product.


Products: Ibm Content Collector.

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

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

## Is CVE-2015-0146 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-4757](https://insights.sbomify.com/CVE-2014-4757/): Missing authorization in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-0146 is a low-severity missing authorization vulnerability in n/a, published on 18 Mar 2015. 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-2015-0146 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-0146/ (Markdown: https://insights.sbomify.com/CVE-2015-0146/index.md)
```

## Sources

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

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