# CVE-2019-10391: Jenkins IBM AppScan Plugin showed plain text password in job configuration form fields

> Attackers can view configured passwords in plain text within job configuration forms, exposing sensitive credentials to unauthorized users.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-65rj-cgrp-g65w

## What is CVE-2019-10391?

CVE-2019-10391 is a medium-severity vulnerability in Jenkins IBM Application Security on Cloud Plugin, published on 28 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Jenkins IBM Application Security on Cloud Plugin 1.2.4 and earlier transmitted configured passwords in plain text as part of job configuration forms, potentially resulting in their exposure.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2019-10391?

2 open source packages ship an affected version, including com.hcl.security:ibm-application-security. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.hcl.security:ibm-application-security` | Maven | All versions | 1.2.5 |
| `com.hcl.security:ibm-application-security` | Maven | All versions | 1.2.5 |

Products: Jenkins Ibm Application Security on Cloud.

## How do I fix CVE-2019-10391?

Upgrade com.hcl.security:ibm-application-security to 1.2.5 or later.

## Is CVE-2019-10391 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10391 and fix it if it is affected.

What it is: CVE-2019-10391 is a medium-severity vulnerability in Jenkins IBM Application Security on Cloud Plugin, published on 28 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-10391 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.hcl.security:ibm-application-security (Maven): affected all versions; fixed in 1.2.5
- com.hcl.security:ibm-application-security (Maven): affected all versions; fixed in 1.2.5

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-2019-10391/ (Markdown: https://insights.sbomify.com/CVE-2019-10391/index.md)
```

## Sources

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

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