# CVE-2017-1377: Information disclosure in Runbook Automation

> IBM Runbook Automation exposes sensitive information in error messages, potentially aiding attackers in further system exploitation.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 10 Aug 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-39j6-mhhv-2qpx

## What is CVE-2017-1377?

CVE-2017-1377 is a medium-severity vulnerability in IBM Runbook Automation, published on 10 Aug 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Runbook Automation reveals sensitive information in error messages that could be used in further attacks against the system. IBM X-Force ID: 126874.

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

## Which versions are affected by CVE-2017-1377?

It affects 1 product.


Products: Ibm Runbook Automation.

## How do I fix CVE-2017-1377?

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

## Is CVE-2017-1377 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1377 and fix it if it is affected.

What it is: CVE-2017-1377 is a medium-severity vulnerability in IBM Runbook Automation, published on 10 Aug 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-2017-1377 in the wild and no public exploit code.

Affected product: IBM Runbook Automation. 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-2017-1377/ (Markdown: https://insights.sbomify.com/CVE-2017-1377/index.md)
```

## Sources

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

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