{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20799 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-20799 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-20799 is a high-severity vulnerability in n/a, published on 1 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-20799 and fix it if it is affected.\n\nWhat it is: CVE-2018-20799 is a high-severity vulnerability in n/a, published on 1 Mar 2019. 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-2018-20799 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-2018-20799/ (Markdown: https://insights.sbomify.com/CVE-2018-20799/index.md)","id":"CVE-2018-20799","markdown":"https://insights.sbomify.com/CVE-2018-20799/index.md","name":"CVE-2018-20799","record":{"aliases":["GHSA-556r-ph87-2m55"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"pfSense firewall","requires_auth":"none","summary":"Inconsistent IP blocking for failed HTTPS versus SSH authentication allows attackers to bypass intended access restrictions in pfSense.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pfsense","vendor":"netgate"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[],"description":"In pfSense 2.4.4_1, blocking of source IP addresses on the basis of failed HTTPS authentication is inconsistent with blocking of source IP addresses on the basis of failed SSH authentication (the behavior does not match the sshguard documentation), which might make it easier for attackers to bypass intended access restrictions.","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-2018-20799","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Other in n/a","id":"CVE-2018-20800"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2018-20798"},"products":["n/a"],"published":"2019-03-01","related":[{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2019-16915","kev_date_added":null,"published":"2019-09-26"},{"cvss_score":9.6,"headline":"Cross-site scripting in n/a","id":"CVE-2020-21487","kev_date_added":null,"published":"2023-04-04"},{"cvss_score":9.3,"headline":"Cross-site scripting in n/a","id":"CVE-2024-46538","kev_date_added":null,"published":"2024-10-22"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2023-48123","kev_date_added":null,"published":"2023-12-06"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2023-42326","kev_date_added":null,"published":"2023-11-14"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2023-27253","kev_date_added":null,"published":"2023-03-17"},{"cvss_score":8.8,"headline":"Command injection in pfSense CE and pfSense Plus","id":"CVE-2022-24299","kev_date_added":null,"published":"2022-03-31"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Inconsistent IP blocking for failed HTTPS versus SSH authentication allows attackers to bypass intended access restrictions in pfSense.","url":"https://insights.sbomify.com/CVE-2018-20799/"}