{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-28873 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-28873 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-28873 is a high-severity denial of service vulnerability in n/a, published on 17 Mar 2021. 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-28873 and fix it if it is affected.\n\nWhat it is: CVE-2020-28873 is a high-severity denial of service vulnerability in n/a, published on 17 Mar 2021. 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-28873 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-28873/ (Markdown: https://insights.sbomify.com/CVE-2020-28873/index.md)","id":"CVE-2020-28873","markdown":"https://insights.sbomify.com/CVE-2020-28873/index.md","name":"CVE-2020-28873","record":{"aliases":["GHSA-275f-jq4p-wxgw"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"FluxBB forum","requires_auth":"none","summary":"An attacker can cause server CPU and memory exhaustion by submitting an extremely long password to the login form, leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fluxbb","vendor":"fluxbb"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-916","name":"Use of Password Hash With Insufficient Computational Effort"}],"description":"Fluxbb 1.5.11 is affected by a denial of service (DoS) vulnerability by sending an extremely long password via the user login form. When a long password is sent, the password hashing process will result in CPU and memory exhaustion on the server.","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":"Denial of service in n/a","id":"CVE-2020-28873","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Business logic in n/a","id":"CVE-2020-28874"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2020-28872"},"products":["n/a"],"published":"2021-03-17","related":[{"cvss_score":9.8,"headline":"Security feature bypass in FluxBB","id":"CVE-2011-3621","kev_date_added":null,"published":"2020-01-22"},{"cvss_score":9.3,"headline":"Path traversal in n/a","id":"CVE-2014-9574","kev_date_added":null,"published":"2015-02-03"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2014-10029","kev_date_added":null,"published":"2015-01-13"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2021-43677","kev_date_added":null,"published":"2022-01-04"},{"cvss_score":5.8,"headline":"Open redirect in n/a","id":"CVE-2014-10030","kev_date_added":null,"published":"2015-01-13"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2025-44110","kev_date_added":null,"published":"2025-05-15"}],"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":"2026-07-09","vendors":["n/a"]},"summary":"An attacker can cause server CPU and memory exhaustion by submitting an extremely long password to the login form, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2020-28873/"}