{"answers":{"affected":"2 open source packages ship an affected version, including com.walmartlabs.concord:concord-common. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-10591 in the wild and no public exploit code.","fix":"Upgrade com.walmartlabs.concord:concord-common to 1.44.0 or later.","what":"CVE-2020-10591 is a high-severity vulnerability in n/a, published on 15 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-10591 and fix it if it is affected.\n\nWhat it is: CVE-2020-10591 is a high-severity vulnerability in n/a, published on 15 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-10591 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.walmartlabs.concord:concord-common (Maven): affected all versions; fixed in 1.44.0\n- com.walmartlabs.concord:concord-common (Maven): affected all versions; fixed in 1.44.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-2020-10591/ (Markdown: https://insights.sbomify.com/CVE-2020-10591/index.md)","id":"CVE-2020-10591","markdown":"https://insights.sbomify.com/CVE-2020-10591/index.md","name":"CVE-2020-10591","record":{"aliases":["GHSA-6566-9526-52v6"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Concord server","requires_auth":"none","summary":"Remote attackers can discover host information, nodes, API metadata, and usernames via unsafe CORS configuration in Concord.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"concord","vendor":"walmart"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"An issue was discovered in Walmart Labs Concord before 1.44.0. CORS Access-Control-Allow-Origin headers have a potentially unsafe dependency on Origin headers, and are not configurable. This allows remote attackers to discover host information, nodes, API metadata, and references to usernames via api/v1/apikey.","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":"Exposure of Sensitive Information to an Unauthorized Actor in Concord","id":"CVE-2020-10591","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2020-10592"},"packages":[{"ecosystem":"Maven","fixed":["1.44.0"],"introduced":["0"],"last_affected":[],"package":"com.walmartlabs.concord:concord-common","purl":null,"source":"GHSA-6566-9526-52v6"},{"ecosystem":"Maven","fixed":["1.44.0"],"introduced":["0"],"last_affected":[],"package":"com.walmartlabs.concord:concord-common","purl":"pkg:maven/com.walmartlabs.concord/concord-common","source":"GHSA-6566-9526-52v6"}],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2020-10590"},"products":["n/a"],"published":"2020-03-15","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Remote attackers can discover host information, nodes, API metadata, and usernames via unsafe CORS configuration in Concord.","url":"https://insights.sbomify.com/CVE-2020-10591/"}