Miggo Logo

CVE-2025-53676: Jenkins Xooa Plugin vulnerability exposes unencrypted tokens to authenticated users

4.3

CVSS Score
3.1

Basic Information

EPSS Score
0.03907%
Published
7/9/2025
Updated
7/9/2025
KEV Status
No
Technology
TechnologyJava

Technical Details

CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Package NameEcosystemVulnerable VersionsFirst Patched Version
io.jenkins.plugins:xooamaven<= 0.0.7

Vulnerability Intelligence
Miggo AIMiggo AI

Miggo AIRoot Cause Analysis

The vulnerability lies in the insecure storage of the Xooa Deployment Token. The analysis of the GlobConfig.java file reveals that the setDeploymentToken method takes the deployment token as a string and saves it without any encryption. The save() method, inherited from GlobalConfiguration, persists the object's state to an XML file, io.jenkins.plugins.xooa.GlobConfig.xml. Consequently, the token is stored in plaintext in this file. The getDeploymentToken method retrieves this unencrypted token. Any user with access to the Jenkins controller's file system can read this file and obtain the token. Additionally, any other part of Jenkins with sufficient permissions could potentially access this token by calling the getDeploymentToken method. The security advisory confirms this finding, stating that the token is stored unencrypted in the global configuration file. Since there is no patch available, the current implementation remains vulnerable.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

WAF Protection Rules

WAF Rule

J*nkins Xoo* Plu*in *.*.* *n* **rli*r stor*s t** Xoo* **ploym*nt Tok*n un*n*rypt** in its *lo**l *on*i*ur*tion *il* on t** J*nkins *ontroll*r, w**r* it **n ** vi*w** *y us*rs wit* ****ss to t** J*nkins *ontroll*r *il* syst*m.

Reasoning

T** vuln*r**ility li*s in t** ins**ur* stor*** o* t** Xoo* **ploym*nt Tok*n. T** *n*lysis o* t** `*lo**on*i*.j*v*` *il* r*v**ls t**t t** `s*t**ploym*ntTok*n` m*t*o* t*k*s t** **ploym*nt tok*n *s * strin* *n* s*v*s it wit*out *ny *n*ryption. T** `s*v*