{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20798 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-20798 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-20798 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-20798 and fix it if it is affected.\n\nWhat it is: CVE-2018-20798 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-20798 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-20798/ (Markdown: https://insights.sbomify.com/CVE-2018-20798/index.md)","id":"CVE-2018-20798","markdown":"https://insights.sbomify.com/CVE-2018-20798/index.md","name":"CVE-2018-20798","record":{"aliases":["GHSA-pjhq-f4xq-m288"],"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":"Incompatible block durations between pfSense and sshguard allow attackers to bypass intended access restrictions.","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":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"The expiretable configuration in pfSense 2.4.4_1 establishes block durations that are incompatible with the block durations implemented by sshguard, 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-20798","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":"Security feature bypass in n/a","id":"CVE-2018-20799"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-20797"},"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":"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-05","vendors":["n/a"]},"summary":"Incompatible block durations between pfSense and sshguard allow attackers to bypass intended access restrictions.","url":"https://insights.sbomify.com/CVE-2018-20798/"}