# CVE-2016-1603: Information disclosure in NetIQ IDM ServiceNow

> Logged-in users can access sensitive cryptographic attributes due to an information leak in the NetIQ IDM ServiceNow Driver.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 23 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7h2r-f38q-p92x

## What is CVE-2016-1603?

CVE-2016-1603 is a medium-severity vulnerability in NetIQ IDM ServiceNow, published on 23 Mar 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An information leak in the NetIQ IDM ServiceNow Driver before 1.0.0.1 could expose cryptographic attributes to logged-in users.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2016-1603?

It affects 1 product.


Products: Novell Netiq Idm Servicenow Driver.

## How do I fix CVE-2016-1603?

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

## Is CVE-2016-1603 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1603 and fix it if it is affected.

What it is: CVE-2016-1603 is a medium-severity vulnerability in NetIQ IDM ServiceNow, published on 23 Mar 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-1603 in the wild and no public exploit code.

Affected product: NetIQ IDM ServiceNow. 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-2016-1603/ (Markdown: https://insights.sbomify.com/CVE-2016-1603/index.md)
```

## Sources

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

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