{"answers":{"affected":"2 open source packages ship an affected version, including semantic-release. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-31051 in the wild and no public exploit code.","fix":"Upgrade semantic-release to 19.0.3 or later.","what":"CVE-2022-31051 is a medium-severity vulnerability in semantic-release, published on 9 Jun 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-31051 and fix it if it is affected.\n\nWhat it is: CVE-2022-31051 is a medium-severity vulnerability in semantic-release, published on 9 Jun 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-31051 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- semantic-release (npm): affected from 17.0.4; fixed in 19.0.3\n- semantic-release (npm): affected from 17.0.4; fixed in 19.0.3\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-2022-31051/ (Markdown: https://insights.sbomify.com/CVE-2022-31051/index.md)","id":"CVE-2022-31051","markdown":"https://insights.sbomify.com/CVE-2022-31051/index.md","name":"CVE-2022-31051","record":{"aliases":["GHSA-x2pg-mjhr-2m5x"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"npm version management library","requires_auth":"high_privilege","summary":"Attackers can view sensitive secrets in semantic-release logs if specific characters are present and repository access requires URL credential injection.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"semantic-release","vendor":"semantic-release_project"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"semantic-release is an open source npm package for automated version management and package publishing. In affected versions secrets that would normally be masked by semantic-release can be accidentally disclosed if they contain characters that are excluded from uri encoding by `encodeURI`. Occurrence is further limited to execution contexts where push access to the related repository is not available without modifying the repository url to inject credentials. Users are advised to upgrade. Users unable to upgrade should ensure that secrets that do not contain characters that are excluded from encoding with `encodeURI` when included in a URL are already masked properly.","ecosystems":["npm"],"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":"Exposure of Sensitive Information to an Unauthorized Actor in semantic-release","id":"CVE-2022-31051","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":2,"n_references":4,"next":{"headline":"URL previews can crash Synapse media repositories or Synapse monoliths","id":"CVE-2022-31052"},"packages":[{"ecosystem":"npm","fixed":["19.0.3"],"introduced":["17.0.4"],"last_affected":[],"package":"semantic-release","purl":null,"source":"GHSA-x2pg-mjhr-2m5x"},{"ecosystem":"npm","fixed":["19.0.3"],"introduced":["17.0.4"],"last_affected":[],"package":"semantic-release","purl":"pkg:npm/semantic-release","source":"GHSA-x2pg-mjhr-2m5x"}],"prev":{"headline":"Insufficient Session Expiration in TYPO3 Admin Tool","id":"CVE-2022-31050"},"products":["semantic-release"],"published":"2022-06-09","related":[{"cvss_score":8.1,"headline":"Secret disclosure in semantic-release","id":"CVE-2020-26226","kev_date_added":null,"published":"2020-11-18"}],"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-04-23","vendors":["semantic-release"]},"summary":"Attackers can view sensitive secrets in semantic-release logs if specific characters are present and repository access requires URL credential injection.","url":"https://insights.sbomify.com/CVE-2022-31051/"}