{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-43762 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-43762 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-43762 is a high-severity denial of service vulnerability in B\u0026R APROL, published on 8 Feb 2023. 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-43762 and fix it if it is affected.\n\nWhat it is: CVE-2022-43762 is a high-severity denial of service vulnerability in B\u0026R APROL, published on 8 Feb 2023. 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-2022-43762 in the wild and no public exploit code.\n\nAffected product: B\u0026R APROL. 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-43762/ (Markdown: https://insights.sbomify.com/CVE-2022-43762/index.md)","id":"CVE-2022-43762","markdown":"https://insights.sbomify.com/CVE-2022-43762/index.md","name":"CVE-2022-43762","record":{"aliases":["GHSA-56vg-qgwv-6h64"],"analysis":{"component_type":"ics_ot","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Industrial Automation Server","requires_auth":"none","summary":"Attackers can cause memory leaks in the APROL Tbase server by sending messages, potentially leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ABB","cpe":[{"product":"industrial_automation_aprol","vendor":"br-automation"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"Lack of verification in B\u0026R APROL\nTbase server versions \u003c R 4.2-07 may lead to memory leaks when receiving messages","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":"Memory leak when receiving messages in APROL Tbase server","id":"CVE-2022-43762","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Lack of checking preconditions in APROL","id":"CVE-2022-43763"},"packages":[],"prev":{"headline":"Lack of authentication when managing APROL database","id":"CVE-2022-43761"},"products":["B\u0026R APROL"],"published":"2023-02-08","related":[{"cvss_score":9.8,"headline":"Buffer overflow when changing configuration on Tbase Server","id":"CVE-2022-43764","kev_date_added":null,"published":"2023-02-08"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-19872","kev_date_added":null,"published":"2020-11-27"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-19874","kev_date_added":null,"published":"2020-11-27"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-19875","kev_date_added":null,"published":"2020-11-27"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-19876","kev_date_added":null,"published":"2020-11-27"},{"cvss_score":9.4,"headline":"Lack of authentication when managing APROL database","id":"CVE-2022-43761","kev_date_added":null,"published":"2023-02-08"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-25","vendors":["B\u0026R Industrial Automation"]},"summary":"Attackers can cause memory leaks in the APROL Tbase server by sending messages, potentially leading to denial of service.","url":"https://insights.sbomify.com/CVE-2022-43762/"}