dbcve.org
Lambdatest AutomationApplication · Jenkins

CVE-2023-46653

MEDIUM · 6.5 CVSS v3.1 Published 2023-10-25
Fix available
A fix is available. Upgrade to 1.21.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 lambdatest-automation Plugin 1.20.10 and earlier logs LAMBDATEST Credentials access token at the INFO level, potentially resulting in its exposure.

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 lambdatest-automation Plugin version 1.20.10 and earlier writes LAMBDATEST access tokens to log files at INFO log level. This causes sensitive authentication credentials to be persisted in logs that may be accessible to unauthorized users or exposed through log aggregation systems.

MitigationUpgrade the lambdatest-automation Plugin to version 1.20.11 or later which addresses the improper credential logging. If immediate upgrade is not possible, review and secure log file access controls and rotate any exposed tokens.

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
Lambdatest AutomationApplication
Affected:< 1.21.0

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
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 checks

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

  1. Verify lambdatest-automation plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'lambdatest-automation' or check the plugin directory $JENKINS_HOME/plugins for the lambdatest-automation plugin folder
    Affected if The plugin is present in the Jenkins instance
  2. Identify the installed plugin version
    In Jenkins > Manage Jenkins > Manage Plugins > Installed, locate the lambdatest-automation plugin and note the version number displayed in the 'Version' column
    Affected if The installed version is 1.20.10 or earlier (any version below 1.21.0)
  3. Confirm LAMBDATEST credentials are configured in Jenkins
    Check Jenkins job configurations or global credentials for LAMBDATEST_API_KEY, LAMBDATEST_USERNAME, or similar LAMBDATEST access token variables. Look in: Manage Jenkins > Manage Credentials, or in specific job configurations under 'Build Environment' or 'Build Steps'
    Affected if LAMBDATEST access tokens or API credentials are stored or used in Jenkins jobs
  4. Inspect Jenkins logs for exposed tokens
    Examine Jenkins logs (typically found in $JENKINS_HOME/logs/ or the system log output) for the string 'LAMBDATEST' or fragments resembling access tokens (typically alphanumeric strings of 20+ characters). Search log files for patterns like 'LAMBDATEST_ACCESS_TOKEN' or 'LT_ACCESS_KEY' appearing at INFO log level
    Affected if Log files contain plain-text LAMBDATEST access tokens or API keys

A user is affected if they have the lambdatest-automation plugin installed at version 1.20.10 or earlier AND have LAMBDATEST credentials configured in Jenkins, with those credentials appearing in log files.

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 1.21.0 or later
Fixed in 1.21.0
Interim mitigation

Upgrade the lambdatest-automation Plugin to version 1.20.11 or later which addresses the improper credential logging. If immediate upgrade is not possible, review and secure log file access controls and rotate any exposed tokens.

Recommended fix High confidence

1.21.0

  1. Navigate to the Jenkins dashboard
  2. Go to 'Manage Jenkins'
  3. Click on 'Manage Plugins'
  4. Select the 'Updates' tab
  5. Locate the 'lambdatest-automation' plugin in the list
  6. If an update is available, select the plugin and click 'Download now and install after restart'
  7. Wait for the plugin to update to version 1.21.0 or later
  8. Restart Jenkins to complete the installation

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

Fix this in Lambdatest Automation Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-46653 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2023-46653 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