What is CVE-2019-10391?

CVE-2019-10391 is a medium-severity security vulnerability in com.hcl.security:ibm-application-security (maven), affecting versions <= 1.2.4. It is fixed in 1.2.5.

How severe is CVE-2019-10391?

CVE-2019-10391 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of com.hcl.security:ibm-application-security are affected by CVE-2019-10391?

com.hcl.security:ibm-application-security (maven) versions <= 1.2.4 is affected.

Is there a fix for CVE-2019-10391?

Yes. CVE-2019-10391 is fixed in 1.2.5. Upgrade to this version or later.

Is CVE-2019-10391 exploitable, and should I be worried?

Whether CVE-2019-10391 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2019-10391 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2019-10391

Q: How severe is CVE-2019-10391?

CVE-2019-10391 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of com.hcl.security:ibm-application-security are affected by CVE-2019-10391?

com.hcl.security:ibm-application-security (maven) versions <= 1.2.4 is affected.

Q: Is there a fix for CVE-2019-10391?

Yes. CVE-2019-10391 is fixed in 1.2.5. Upgrade to this version or later.

Q: Is CVE-2019-10391 exploitable, and should I be worried?

Whether CVE-2019-10391 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2019-10391 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2019-10391?

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

Summary

Jenkins IBM AppScan Plugin showed plain text password in job configuration form fields

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. This plugin has bee deprecated.

Impact

CVE-2019-10391 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.2.5); upgrading removes the vulnerable code path.

Affected versions

com.hcl.security:ibm-application-security (<= 1.2.4)

Security releases

com.hcl.security:ibm-application-security → 1.2.5 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2019-10391? CVE-2019-10391 is a medium-severity security vulnerability in com.hcl.security:ibm-application-security (maven), affecting versions <= 1.2.4. It is fixed in 1.2.5.
How severe is CVE-2019-10391? CVE-2019-10391 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of com.hcl.security:ibm-application-security are affected by CVE-2019-10391? com.hcl.security:ibm-application-security (maven) versions <= 1.2.4 is affected.
Is there a fix for CVE-2019-10391? Yes. CVE-2019-10391 is fixed in 1.2.5. Upgrade to this version or later.
Is CVE-2019-10391 exploitable, and should I be worried? Whether CVE-2019-10391 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2019-10391 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2019-10391? Upgrade com.hcl.security:ibm-application-security to 1.2.5 or later.