{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24756 exists.","fix":"No fix has been published for CVE-2022-24756 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-24756 is a high-severity denial of service vulnerability in bareos, published on 15 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-24756 and fix it if it is affected.\n\nWhat it is: CVE-2022-24756 is a high-severity denial of service vulnerability in bareos, published on 15 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24756 exists.\n\nAffected product: bareos. 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-2022-24756/ (Markdown: https://insights.sbomify.com/CVE-2022-24756/index.md)","id":"CVE-2022-24756","markdown":"https://insights.sbomify.com/CVE-2022-24756/index.md","name":"CVE-2022-24756","record":{"aliases":["GHSA-jh55-4wgw-xc9j","UBUNTU-CVE-2022-24756"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Bareos backup server","requires_auth":"none","summary":"An attacker can cause a denial of service in Bareos Director by flooding failed PAM authentication attempts, leading to memory exhaustion.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"bareos","vendor":"bareos"}],"cvss":{"score":7.5,"severity":"high","source":"cna","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-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"Bareos is open source software for backup, archiving, and recovery of data for operating systems. When Bareos Director \u003e= 18.2 but prior to 21.1.0, 20.0.6, and 19.2.12 is built and configured for PAM authentication, a failed PAM authentication will leak a small amount of memory. An attacker that is able to use the PAM Console (i.e. by knowing the shared secret or via the WebUI) can flood the Director with failing login attempts which will eventually lead to an out-of-memory condition in which the Director will not work anymore. Bareos Director versions 21.1.0, 20.0.6 and 19.2.12 contain a Bugfix for this problem. Users who are unable to upgrade may disable PAM authentication as a workaround.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Missing Release of Memory after Effective Lifetime in Bareos Director","id":"CVE-2022-24756","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":0,"n_references":5,"next":{"headline":"Sensitive Auth \u0026 Cookie data stored in Jupyter server logs","id":"CVE-2022-24757"},"packages":[],"prev":{"headline":"Incorrect Authorization in Bareos Director","id":"CVE-2022-24755"},"products":["bareos"],"published":"2022-03-15","related":[{"cvss_score":8.1,"headline":"Incorrect Authorization in Bareos Director","id":"CVE-2022-24755","kev_date_added":null,"published":"2022-03-15"},{"cvss_score":7.8,"headline":"Race condition in n/a","id":"CVE-2017-14610","kev_date_added":null,"published":"2017-09-20"},{"cvss_score":6.8,"headline":"Authentication bypass in Bareos","id":"CVE-2020-4042","kev_date_added":null,"published":"2020-07-10"},{"cvss_score":6,"headline":"Heap-based Buffer Overflow in Bareos Director","id":"CVE-2020-11061","kev_date_added":null,"published":"2020-07-10"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["bareos"]},"summary":"An attacker can cause a denial of service in Bareos Director by flooding failed PAM authentication attempts, leading to memory exhaustion.","url":"https://insights.sbomify.com/CVE-2022-24756/"}