Convertigo Mobile PlatformApplication · Jenkins
CVE-2022-34199
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 Convertigo Mobile Platform Plugin 1.1 and earlier stores passwords unencrypted in job config.xml files on the Jenkins controller where they can be viewed by users with 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 Convertigo Mobile Platform Plugin version 1.1 and earlier stores passwords in plain text within job config.xml files on the Jenkins controller. Users with Extended Read permission (a built-in Jenkins permission allowing configuration viewing) can retrieve these passwords from the configuration files, or anyone with filesystem access to the Jenkins controller can read them directly from disk.
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
Convertigo Mobile PlatformApplication
<= 1.1CVSS 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 Convertigo Mobile Platform Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Convertigo Mobile Platform', or inspect the plugin directory at $JENKINS_HOME/plugins/ for a folder named 'convertigo-mobile-platform'Affected if The plugin is present and its version is 1.1 or earlier (typically found in the plugin's MANIFEST.MF file or the plugins table)
-
Identify jobs using the Convertigo pluginSearch job config.xml files for the Convertigo plugin namespace or configuration elements. Run: grep -r 'convertigo' $JENKINS_HOME/jobs/*/config.xml or inspect individual job configurations under Jenkins > [Job Name] > ConfigureAffected if Any job configuration contains Convertigo-related elements, indicating the plugin is in use
-
Check for plaintext passwords in job config.xmlOpen the config.xml file of a job using Convertigo (located at $JENKINS_HOME/jobs/[jobname]/config.xml) and look for password fields within Convertigo configuration sections. Search for <password> or similar plaintext credential entriesAffected if The config.xml contains plaintext passwords stored in plain text rather than masked or encrypted within Convertigo configuration sections
-
Verify Extended Read permission exposureConfirm if any users or groups have the Extended Read permission (Jenkins > Manage Jenkins > Manage Users and check authorization matrix). Users with this permission can view job configuration files through the UI without full admin rightsAffected if Extended Read permission is granted to non-admin users, allowing them to retrieve plaintext passwords from job configurations via the UI
-
Check filesystem access to config.xml filesVerify file permissions on job directories at $JENKINS_HOME/jobs/. Any user or process with read access to these directories can directly read plaintext passwords from config.xml filesAffected if File permissions allow non-admin users or processes to read job config.xml files directly from disk
You are affected if the Convertigo Mobile Platform Plugin version 1.1 or earlier is installed and any job configurations contain plaintext passwords stored in Convertigo-related config elements, especially if Extended Read permission is enabled or filesystem access is not restricted.
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.
dbcve · scopedUpdate to a patched version of the Convertigo Mobile Platform Plugin when available, then identify all affected jobs, rotate exposed passwords, and re-configure credentials using Jenkins' built-in credentials provider with appropriate encryption rather than storing plaintext passwords in job configurations.
Convertigo Mobile Platform Plugin version > 1.1 (check Jenkins plugin repository for latest available version)
- Navigate to Jenkins > Manage Jenkins > Manage Plugins
- Go to the 'Available' tab and search for 'Convertigo Mobile Platform'
- If an update is available, select the plugin and click 'Download now and install after restart'
- Alternatively, go to the 'Updates' tab to find the Convertigo Mobile Platform plugin update
- After installation, restart Jenkins to apply the update
- Verify the plugin has been updated to a version greater than 1.1
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Convertigo Mobile Platform
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34199 — 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-2022-34199 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