Nouvola DivecloudApplication · Jenkins
CVE-2025-53670
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins Nouvola DiveCloud Plugin 1.08 and earlier stores DiveCloud API Keys and Credentials Encryption Keys unencrypted in job config.xml files on the Jenkins controller, where they can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins Nouvola DiveCloud Plugin version 1.08 and earlier stores DiveCloud API Keys and Credentials Encryption Keys in plaintext within job config.xml files on the Jenkins controller. This allows any user with Item/Extended Read permission or filesystem access to view these sensitive credentials in cleartext.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Nouvola DivecloudApplication
<= 1.08CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify DiveCloud plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Nouvola DiveCloud' or run the Jenkins CLI command: jenkins-plugin-cli --list-plugins | grep -i divecloudAffected if The Nouvola DiveCloud plugin appears in the installed plugins list
-
Confirm plugin versionClick on the Nouvola DiveCloud plugin in the Installed plugins list and view the Version fieldAffected if The installed version is 1.08 or any earlier version number
-
Locate job config.xml filesOn the Jenkins controller filesystem, navigate to the JENKINS_HOME/jobs directory and list each job folderAffected if Job directories with config.xml files exist under JENKINS_HOME/jobs
-
Search for plaintext credentials in config.xmlOpen config.xml files from each job and search for plaintext strings containing 'DiveCloud' or look for API Keys and Credentials Encryption Keys stored as cleartext valuesAffected if Any config.xml file contains DiveCloud API Keys or Credentials Encryption Keys in plaintext form
If the plugin version is 1.08 or earlier and any job config.xml contains plaintext DiveCloud API Keys or Credentials Encryption Keys, the environment is affected.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately rotate any exposed DiveCloud API Keys and Credentials Encryption Keys, then upgrade to a patched plugin version if available. Restrict Item/Extended Read permissions and filesystem access to mitigate exposure until the fix is applied.
Fix this in Nouvola Divecloud
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,032.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53670 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-53670 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data