{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-7346 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-7346 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-7346 is a high-severity vulnerability in Progress OpenEdge, published on 3 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-7346 and fix it if it is affected.\n\nWhat it is: CVE-2024-7346 is a high-severity vulnerability in Progress OpenEdge, published on 3 Sep 2024. 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-2024-7346 in the wild and no public exploit code.\n\nAffected product: Progress OpenEdge. 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-2024-7346/ (Markdown: https://insights.sbomify.com/CVE-2024-7346/index.md)","id":"CVE-2024-7346","markdown":"https://insights.sbomify.com/CVE-2024-7346/index.md","name":"CVE-2024-7346","record":{"aliases":["GHSA-jw9p-3gc4-84rw"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Progress OpenEdge","requires_auth":"none","summary":"Attackers can bypass TLS host name validation using default certificates, requiring replacement with CA-signed certificates to ensure secure connections.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ProgressSoftware","cpe":[{"product":"openedge","vendor":"progress"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"},{"id":"CWE-297","name":"Improper Validation of Certificate with Host Mismatch"}],"description":"Host name validation for TLS certificates is bypassed when the installed OpenEdge default certificates are used to perform the TLS handshake for a networked connection.  This has been corrected so that default certificates are no longer capable of overriding host name validation and will need to be replaced where full TLS certificate validation is needed for network security.  The existing certificates should be replaced with CA-signed certificates from a recognized certificate authority that contain the necessary information to support host name validation.","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":"Client connections using default TLS certificates from OpenEdge may bypass TLS host name validation","id":"CVE-2024-7346","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"NGINX MP4 module vulnerability","id":"CVE-2024-7347"},"packages":[],"prev":{"headline":"Direct local client connections to MS Agents can bypass authentication","id":"CVE-2024-7345"},"products":["OpenEdge"],"published":"2024-09-03","related":[{"cvss_score":10,"headline":"Authentication Bypass in OpenEdge Authentication Gateway and AdminServer","id":"CVE-2024-1403","kev_date_added":null,"published":"2024-02-27"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2007-2417","kev_date_added":null,"published":"2007-07-15"},{"cvss_score":9.8,"headline":"Misconfiguration in n/a","id":"CVE-2015-9245","kev_date_added":null,"published":"2017-10-31"},{"cvss_score":9.1,"headline":"Progress Application Server (PAS) for OpenEdge File Upload via Directory Traversal","id":"CVE-2023-40051","kev_date_added":null,"published":"2024-01-18"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2023-34203","kev_date_added":null,"published":"2023-06-23"},{"cvss_score":8.3,"headline":"Direct local client connections to MS Agents can bypass authentication","id":"CVE-2024-7345","kev_date_added":null,"published":"2024-09-03"},{"cvss_score":8.3,"headline":"Unauthenticated Content Injection in OpenEdge Management web interface via ActiveMQ discovery service","id":"CVE-2024-7654","kev_date_added":null,"published":"2024-09-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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-03","vendors":["Progress"]},"summary":"Attackers can bypass TLS host name validation using default certificates, requiring replacement with CA-signed certificates to ensure secure connections.","url":"https://insights.sbomify.com/CVE-2024-7346/"}