VYPR
High severityNVD Advisory· Published Oct 16, 2019· Updated Aug 4, 2024

CVE-2019-10443

CVE-2019-10443

Description

Jenkins iceScrum Plugin 1.1.4 and earlier stores credentials in plaintext in job config.xml files, allowing users with Extended Read or file system access to obtain them.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Jenkins iceScrum Plugin 1.1.4 and earlier stores credentials in plaintext in job config.xml files, allowing users with Extended Read or file system access to obtain them.

Vulnerability

Description

The Jenkins iceScrum Plugin, versions 1.1.4 and earlier, stores credentials in plaintext within job config.xml files on the Jenkins master [1][3]. This violates security best practices for credential handling.

Exploitation

An attacker with Extended Read permission (or direct access to the Jenkins master file system) can read these config.xml files to obtain the plaintext credentials [4]. No authentication is required beyond the initial access, making exploitation straightforward.

Impact

Successful exploitation leads to disclosure of credentials stored by the iceScrum plugin. These credentials could be used to access other systems or services, potentially escalating privileges or enabling further attacks within the CI/CD pipeline [1].

Mitigation

Jenkins has released version 1.1.6 of the iceScrum Plugin, which encrypts credential storage [1]. Users are strongly advised to update immediately. As a workaround, restrict Extended Read permissions and limit file system access to the Jenkins master.

AI Insight generated on May 22, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
org.jenkins-ci.plugins:icescrumMaven
< 1.1.51.1.5

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

6

News mentions

0

No linked articles in our index yet.