{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16248 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16248 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16248 is a medium-severity vulnerability in n/a, published on 11 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-16248 and fix it if it is affected.\n\nWhat it is: CVE-2019-16248 is a medium-severity vulnerability in n/a, published on 11 Sep 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-16248 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-2019-16248/ (Markdown: https://insights.sbomify.com/CVE-2019-16248/index.md)","id":"CVE-2019-16248","markdown":"https://insights.sbomify.com/CVE-2019-16248/index.md","name":"CVE-2019-16248","record":{"aliases":["GHSA-72jh-q3w2-7xjq"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Telegram Android app","requires_auth":"low_privilege","summary":"Telegram Android fails to delete shared media files when using the delete for feature, allowing recipients to retain access to images despite sender deletion.","user_interaction":"not_required","vuln_class":"business_logic"},"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:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"The \"delete for\" feature in Telegram before 5.11 on Android does not delete shared media files from the Telegram Images directory. In other words, there is a potentially misleading UI indication that a sender can remove a recipient's copy of a previously sent image (analogous to supported functionality in which a sender can remove a recipient's copy of a previously sent message).","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":"Business logic in n/a","id":"CVE-2019-16248","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Out-of-bounds Read in OpenCV","id":"CVE-2019-16249"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-16247"},"products":["n/a"],"published":"2019-09-11","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Telegram Android fails to delete shared media files when using the delete for feature, allowing recipients to retain access to images despite sender deletion.","url":"https://insights.sbomify.com/CVE-2019-16248/"}