{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-11061 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-11061 is a medium-severity memory corruption vulnerability in Debian Debian Linux, published on 10 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-11061 and fix it if it is affected.\n\nWhat it is: CVE-2020-11061 is a medium-severity memory corruption vulnerability in Debian Debian Linux, published on 10 Jul 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-11061 in the wild and no public exploit code.\n\nAffected product: Debian Debian Linux. 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-11061/ (Markdown: https://insights.sbomify.com/CVE-2020-11061/index.md)","id":"CVE-2020-11061","markdown":"https://insights.sbomify.com/CVE-2020-11061/index.md","name":"CVE-2020-11061","record":{"aliases":["CLEANSTART-2024-OX27386","DEBIAN-CVE-2020-11061","DLA-2353-1","GHSA-mm45-cg35-54j4","UBUNTU-CVE-2020-11061"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Bareos Director","requires_auth":"low_privilege","summary":"A malicious client can trigger a heap overflow in Bareos Director via oversized digest strings, potentially leading to code execution or service disruption.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"bareos","vendor":"bareos"},{"product":"debian_linux","vendor":"debian"}],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"In Bareos Director less than or equal to 16.2.10, 17.2.9, 18.2.8, and 19.2.7, a heap overflow allows a malicious client to corrupt the director's memory via oversized digest strings sent during initialization of a verify job. Disabling verify jobs mitigates the problem. This issue is also patched in Bareos versions 19.2.8, 18.2.9 and 17.2.10.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Heap-based Buffer Overflow in Bareos Director","id":"CVE-2020-11061","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"debian:debian_linux","products":["debian:debian_linux"],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Reflexive XSS in GLPI","id":"CVE-2020-11062"},"packages":[],"prev":{"headline":"Remote Code Execution in GLPI","id":"CVE-2020-11060"},"products":["Bareos Director"],"published":"2020-07-10","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":7.5,"headline":"Missing Release of Memory after Effective Lifetime in Bareos Director","id":"CVE-2022-24756","kev_date_added":null,"published":"2022-03-15"},{"cvss_score":6.8,"headline":"Authentication bypass in Bareos","id":"CVE-2020-4042","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Bareos GmbH \u0026 Co. KG"]},"summary":"A malicious client can trigger a heap overflow in Bareos Director via oversized digest strings, potentially leading to code execution or service disruption.","url":"https://insights.sbomify.com/CVE-2020-11061/"}