{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-31323 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-31323 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-31323 is a medium-severity memory corruption vulnerability in n/a, published on 18 May 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-31323 and fix it if it is affected.\n\nWhat it is: CVE-2021-31323 is a medium-severity memory corruption vulnerability in n/a, published on 18 May 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-31323 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-2021-31323/ (Markdown: https://insights.sbomify.com/CVE-2021-31323/index.md)","id":"CVE-2021-31323","markdown":"https://insights.sbomify.com/CVE-2021-31323/index.md","name":"CVE-2021-31323","record":{"aliases":["GHSA-7fqj-v4vw-h2vm"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Telegram messaging app","requires_auth":"none","summary":"A remote attacker can trigger a heap buffer overflow in Telegram clients via malicious animated stickers, potentially leading to code execution or memory disclosure.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"telegram","vendor":"telegram"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"Telegram Android \u003c7.1.0 (2090), Telegram iOS \u003c7.1, and Telegram macOS \u003c7.1 are affected by a Heap Buffer Overflow in the LottieParserImpl::parseDashProperty function of their custom fork of the rlottie library. A remote attacker might be able to access heap memory out-of-bounds on a victim device via a malicious animated sticker.","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 corruption in n/a","id":"CVE-2021-31323","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2021-31324"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2021-31322"},"products":["n/a"],"published":"2021-05-18","related":[{"cvss_score":8.8,"headline":"Other in n/a","id":"CVE-2019-10044","kev_date_added":null,"published":"2019-03-25"},{"cvss_score":8.1,"headline":"Server-side request forgery in n/a","id":"CVE-2018-20436","kev_date_added":null,"published":"2018-12-24"},{"cvss_score":7.1,"headline":"Improper multimedia file attachment validation in Telegram for Android app","id":"CVE-2024-7014","kev_date_added":null,"published":"2024-07-23"},{"cvss_score":7.1,"headline":"Memory corruption in n/a","id":"CVE-2021-31320","kev_date_added":null,"published":"2021-05-18"},{"cvss_score":7.1,"headline":"Memory corruption in n/a","id":"CVE-2021-31321","kev_date_added":null,"published":"2021-05-18"},{"cvss_score":6.8,"headline":"Auth bypass in n/a","id":"CVE-2018-15543","kev_date_added":null,"published":"2018-10-09"},{"cvss_score":6.5,"headline":"Other in n/a","id":"CVE-2020-12474","kev_date_added":null,"published":"2020-05-01"}],"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-03","vendors":["n/a"]},"summary":"A remote attacker can trigger a heap buffer overflow in Telegram clients via malicious animated stickers, potentially leading to code execution or memory disclosure.","url":"https://insights.sbomify.com/CVE-2021-31323/"}