{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-39310 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-39310 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-39310 is a medium-severity missing authorization vulnerability in gocd, published on 14 Oct 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-39310 and fix it if it is affected.\n\nWhat it is: CVE-2022-39310 is a medium-severity missing authorization vulnerability in gocd, published on 14 Oct 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-39310 in the wild and no public exploit code.\n\nAffected product: gocd. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-39310/ (Markdown: https://insights.sbomify.com/CVE-2022-39310/index.md)","id":"CVE-2022-39310","markdown":"https://insights.sbomify.com/CVE-2022-39310/index.md","name":"CVE-2022-39310","record":{"aliases":["GHSA-4fp5-33jh-hgcq"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"GoCD continuous delivery server","requires_auth":"high_privilege","summary":"Authenticated agents can impersonate others to access sensitive work packages, leading to information disclosure in GoCD servers.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"gocd","vendor":"thoughtworks"}],"cvss":{"score":4.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"GoCD is a continuous delivery server. GoCD helps you automate and streamline the build-test-release cycle for continuous delivery of your product. GoCD versions prior to 21.1.0 can allow one authenticated agent to impersonate another agent, and thus receive work packages for other agents due to broken access control and incorrect validation of agent tokens within the GoCD server. Since work packages can contain sensitive information such as credentials intended only for a given job running against a specific agent environment, this can cause accidental information disclosure. Exploitation requires knowledge of agent identifiers and ability to authenticate as an existing agent with the GoCD server. This issue is fixed in GoCD version 21.1.0. There are currently no known workarounds.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Malicious agent may be able to impersonate another agent in GoCD","id":"CVE-2022-39310","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Compromised agents may be able to execute remote code on GoCD Server","id":"CVE-2022-39311"},"packages":[],"prev":{"headline":"GoCD server secret encryption/decryption key leaked to agents during material serialization","id":"CVE-2022-39309"},"products":["gocd"],"published":"2022-10-14","related":[{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2021-43290","kev_date_added":null,"published":"2022-04-14"},{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2021-44659","kev_date_added":null,"published":"2021-12-22"},{"cvss_score":9.4,"headline":"GoCD vulnerable to admin privilege escalation by a malicious internal/existing authenticated user","id":"CVE-2024-56320","kev_date_added":null,"published":"2025-01-03"},{"cvss_score":9.1,"headline":"Compromised agents may be able to execute remote code on GoCD Server","id":"CVE-2022-39311","kev_date_added":null,"published":"2022-10-14"},{"cvss_score":8.8,"headline":"Command Injection/Argument Injection in GoCD","id":"CVE-2022-29184","kev_date_added":null,"published":"2022-05-20"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2021-43286","kev_date_added":null,"published":"2022-04-14"},{"cvss_score":8.8,"headline":"Cross-site request forgery in gocd","id":"CVE-2021-25924","kev_date_added":null,"published":"2021-04-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":["gocd"]},"summary":"Authenticated agents can impersonate others to access sensitive work packages, leading to information disclosure in GoCD servers.","url":"https://insights.sbomify.com/CVE-2022-39310/"}