{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15526 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15526 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15526 is a medium-severity vulnerability in n/a, published on 9 Jul 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-15526 and fix it if it is affected.\n\nWhat it is: CVE-2020-15526 is a medium-severity vulnerability in n/a, published on 9 Jul 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-15526 in the wild and no public exploit code.\n\nAffected product: n/a. 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-15526/ (Markdown: https://insights.sbomify.com/CVE-2020-15526/index.md)","id":"CVE-2020-15526","markdown":"https://insights.sbomify.com/CVE-2020-15526/index.md","name":"CVE-2020-15526","record":{"aliases":["GHSA-q688-9f45-v5fw"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"SQL monitoring tool","requires_auth":"none","summary":"Redgate SQL Monitor allows disabling TLS certificate checks for notifications, enabling man-in-the-middle attacks on alert emails and webhooks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"sql_monitor","vendor":"red-gate"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"In Redgate SQL Monitor 7.1.4 through 10.1.6 (inclusive), the scope for disabling some TLS security certificate checks can extend beyond that defined by various options on the Configuration \u003e Notifications pages to disable certificate checking for alert notifications. These TLS security checks are also ignored during monitoring of VMware machines. This would make SQL Monitor vulnerable to potential man-in-the-middle attacks when sending alert notification emails, posting to Slack or posting to webhooks. The vulnerability is fixed in version 10.1.7.","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":"Security feature bypass in n/a","id":"CVE-2020-15526","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2020-15528"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2020-15525"},"products":["n/a"],"published":"2020-07-09","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2015-9098","kev_date_added":null,"published":"2017-06-22"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2022-47542","kev_date_added":null,"published":"2023-03-30"},{"cvss_score":7.2,"headline":"SQL injection in n/a","id":"CVE-2020-9318","kev_date_added":null,"published":"2020-02-20"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2022-47870","kev_date_added":null,"published":"2023-04-04"}],"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":["n/a"]},"summary":"Redgate SQL Monitor allows disabling TLS certificate checks for notifications, enabling man-in-the-middle attacks on alert emails and webhooks.","url":"https://insights.sbomify.com/CVE-2020-15526/"}