{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-21658 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-21658 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-21658 is a medium-severity denial of service vulnerability in discourse-calendar, published on 30 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-21658 and fix it if it is affected.\n\nWhat it is: CVE-2024-21658 is a medium-severity denial of service vulnerability in discourse-calendar, published on 30 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-21658 in the wild and no public exploit code.\n\nAffected product: discourse-calendar. 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-21658/ (Markdown: https://insights.sbomify.com/CVE-2024-21658/index.md)","id":"CVE-2024-21658","markdown":"https://insights.sbomify.com/CVE-2024-21658/index.md","name":"CVE-2024-21658","record":{"aliases":["GHSA-65f2-9ghp-x8h8"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Discourse calendar plugin","requires_auth":"low_privilege","summary":"A malicious actor can cause excessive bandwidth and disk space usage in Discourse instances via the calendar plugin, requiring an upgrade to mitigate.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"discourse_calendar","vendor":"discourse"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"discourse-calendar is a discourse plugin which adds the ability to create a dynamic calendar in the first post of a topic. The limit on region value length is too generous. This allows a malicious actor to cause a Discourse instance to use excessive bandwidth and disk space. This issue has been patched in main the main branch. There are no workarounds for this vulnerability. Please upgrade as soon as possible.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Insufficient control of region value length in discourse-calendar","id":"CVE-2024-21658","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Argo CD Denial of Service (DoS) Vulnerability Due to Unsafe Array Modification in Multi-threaded Environment","id":"CVE-2024-21661"},"packages":[],"prev":{"headline":"Insufficient control of custom field value sizes","id":"CVE-2024-21655"},"products":["discourse-calendar"],"published":"2024-08-30","related":[{"cvss_score":8,"headline":"Improper escaping of user input in discourse-calendar","id":"CVE-2023-43658","kev_date_added":null,"published":"2023-10-16"},{"cvss_score":6.5,"headline":"Discourse Calendar Event names susceptible to Cross-site Scripting","id":"CVE-2022-31059","kev_date_added":null,"published":"2022-06-14"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-30","vendors":["discourse"]},"summary":"A malicious actor can cause excessive bandwidth and disk space usage in Discourse instances via the calendar plugin, requiring an upgrade to mitigate.","url":"https://insights.sbomify.com/CVE-2024-21658/"}