{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:lambdatest-automation. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-46653 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:lambdatest-automation to 1.21.0 or later.","what":"CVE-2023-46653 is a medium-severity vulnerability in Jenkins lambdatest-automation Plugin, published on 25 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-46653 and fix it if it is affected.\n\nWhat it is: CVE-2023-46653 is a medium-severity vulnerability in Jenkins lambdatest-automation Plugin, published on 25 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-46653 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:lambdatest-automation (Maven): affected all versions; fixed in 1.21.0\n- org.jenkins-ci.plugins:lambdatest-automation (Maven): affected all versions; fixed in 1.21.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-46653/ (Markdown: https://insights.sbomify.com/CVE-2023-46653/index.md)","id":"CVE-2023-46653","markdown":"https://insights.sbomify.com/CVE-2023-46653/index.md","name":"CVE-2023-46653","record":{"aliases":["GHSA-hpv3-f5p7-pxj9"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins LambdaTest plugin","requires_auth":"low_privilege","summary":"Attackers can obtain LambdaTest access tokens from Jenkins logs, compromising cloud testing credentials.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"lambdatest-automation","vendor":"jenkins"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"Jenkins lambdatest-automation Plugin 1.20.10 and earlier logs LAMBDATEST Credentials access token at the INFO level, potentially resulting in its exposure.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Jenkins lambdatest-automation Plugin may expose Credentials access token","id":"CVE-2023-46653","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":2,"n_references":2,"next":{"headline":"Jenkins CloudBees CD Plugin vulnerable to arbitrary file deletion","id":"CVE-2023-46654"},"packages":[{"ecosystem":"Maven","fixed":["1.21.0"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:lambdatest-automation","purl":null,"source":"GHSA-hpv3-f5p7-pxj9"},{"ecosystem":"Maven","fixed":["1.21.0"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:lambdatest-automation","purl":"pkg:maven/org.jenkins-ci.plugins/lambdatest-automation","source":"GHSA-hpv3-f5p7-pxj9"}],"prev":{"headline":"Jenkins lambdatest-automation Plugin missing permission check","id":"CVE-2023-46652"},"products":["Jenkins lambdatest-automation Plugin"],"published":"2023-10-25","related":[{"cvss_score":4.3,"headline":"Jenkins lambdatest-automation Plugin missing permission check","id":"CVE-2023-46652","kev_date_added":null,"published":"2023-10-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["Jenkins Project"]},"summary":"Attackers can obtain LambdaTest access tokens from Jenkins logs, compromising cloud testing credentials.","url":"https://insights.sbomify.com/CVE-2023-46653/"}