SmalltestApplication · Jenkins

CVE-2022-41243

HIGH · 8.1 CVSS v3.1 Published 2022-09-21
Fix available
A fix is available. Upgrade to after 1.0.4 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Jenkins SmallTest Plugin 1.0.4 and earlier does not perform hostname validation when connecting to the configured View26 server that could be abused using a man-in-the-middle attack to intercept these connections.

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 confidence

The Jenkins SmallTest Plugin versions 1.0.4 and earlier fails to validate hostnames when establishing connections to the configured View26 server. This allows an attacker positioned between the Jenkins server and View26 server to intercept and modify traffic through a man-in-the-middle attack.

MitigationUpgrade to Jenkins SmallTest Plugin version 1.0.5 or later which implements proper hostname validation for connections to the View26 server.

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
SmalltestApplication
Affected:<= 1.0.4

CVSS 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Jenkins SmallTest Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'SmallTest' or check the plugin directory $JENKINS_HOME/plugins for smalltest/ directory
    Affected if The plugin directory exists or the plugin appears in the Installed tab with version 1.0.4 or earlier
  2. Verify the installed plugin version
    Check the version manifest file at $JENKINS_HOME/plugins/smalltest/META-INF/MANIFEST.MF or view version in the Jenkins plugin manager UI
    Affected if The version listed is 1.0.4 or earlier (e.g., 1.0.4, 1.0.3, 1.0.2, etc.)
  3. Determine if View26 server is configured
    Check Jenkins configuration files (config.xml) or job configurations for View26 server URL settings, typically under job configuration XML files or system configuration
    Affected if A View26 server URL is configured in Jenkins system settings or in any job configurations using the SmallTest plugin
  4. Check network configuration for View26 connections
    Review network traffic logs or proxy configurations that would show whether connections to View26 are using unvalidated SSL/TLS or cleartext communication
    Affected if Connections to View26 bypass certificate hostname validation (the plugin does not enforce hostname verification)

You are affected if Jenkins SmallTest Plugin version 1.0.4 or earlier is installed AND a View26 server is configured, because the plugin fails to validate hostnames during SSL/TLS connections enabling MITM attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.0.4
Interim mitigation

Upgrade to Jenkins SmallTest Plugin version 1.0.5 or later which implements proper hostname validation for connections to the View26 server.

Recommended fix Moderate confidence

Upgrade to SmallTest plugin version 1.0.5 or later (the first version containing the security fix for CVE-2022-41243)

  1. 1. Navigate to Manage Jenkins > Manage Plugins
  2. 2. Go to the "Installed" tab
  3. 3. Locate the SmallTest plugin in the list
  4. 4. Check if an update is available for the SmallTest plugin
  5. 5. If an update is available, apply the update to upgrade to a fixed version that includes proper hostname validation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Smalltest Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41243 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41243 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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