{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-7339 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-7339 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-7339 is a medium-severity vulnerability in McAfee Database Security, published on 9 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-7339 and fix it if it is affected.\n\nWhat it is: CVE-2020-7339 is a medium-severity vulnerability in McAfee Database Security, published on 9 Dec 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-7339 in the wild and no public exploit code.\n\nAffected product: McAfee Database Security. 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-2020-7339/ (Markdown: https://insights.sbomify.com/CVE-2020-7339/index.md)","id":"CVE-2020-7339","markdown":"https://insights.sbomify.com/CVE-2020-7339/index.md","name":"CVE-2020-7339","record":{"aliases":["GHSA-9gph-vg5f-m5qg"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Database Security Server","requires_auth":"none","summary":"An attacker on the local network can intercept communications between the server and sensors due to the use of SHA1 signed certificates.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"trellix","cpe":[{"product":"database_security","vendor":"mcafee"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"Use of a Broken or Risky Cryptographic Algorithm vulnerability in McAfee Database Security Server and Sensor prior to 4.8.0 in the form of a SHA1 signed certificate that would allow an attacker on the same local network to potentially intercept communication between the Server and Sensors.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Database Security(DBS)-Use of a Broken or Risky Cryptographic Algorithm","id":"CVE-2020-7339","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Authorization vulnerability in MA","id":"CVE-2020-7343"},"packages":[],"prev":{"headline":"Incorrect Permission Assignment for Critical Resource","id":"CVE-2020-7337"},"products":["Database Security"],"published":"2020-12-09","related":[{"cvss_score":9.6,"headline":"Unauthorized deserialization of untrusted data in McAfee DBSec","id":"CVE-2021-23894","kev_date_added":null,"published":"2021-06-02"},{"cvss_score":9,"headline":"Authorized deserialization of untrusted data in McAfee DBSec","id":"CVE-2021-23895","kev_date_added":null,"published":"2021-06-02"},{"cvss_score":6.1,"headline":"Denial of Service in Database Security on Windows","id":"CVE-2021-31850","kev_date_added":null,"published":"2021-12-08"},{"cvss_score":5.9,"headline":"Cross site Scripting (XSS) vulnerability in McAfee DBSec","id":"CVE-2021-31830","kev_date_added":null,"published":"2021-06-03"},{"cvss_score":5.3,"headline":"Data Leakage Vulnerability in McAfee Database Security web interface","id":"CVE-2019-3615","kev_date_added":null,"published":"2019-03-12"},{"cvss_score":4.9,"headline":"Incorrect access to deleted scripts vulnerability in McAfee DBSec","id":"CVE-2021-31831","kev_date_added":null,"published":"2021-06-03"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["McAfee"]},"summary":"An attacker on the local network can intercept communications between the server and sensors due to the use of SHA1 signed certificates.","url":"https://insights.sbomify.com/CVE-2020-7339/"}