{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-15514 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15514 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15514 is a medium-severity vulnerability in n/a, published on 23 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-15514 and fix it if it is affected.\n\nWhat it is: CVE-2019-15514 is a medium-severity vulnerability in n/a, published on 23 Aug 2019. 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-2019-15514 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-15514/ (Markdown: https://insights.sbomify.com/CVE-2019-15514/index.md)","id":"CVE-2019-15514","markdown":"https://insights.sbomify.com/CVE-2019-15514/index.md","name":"CVE-2019-15514","record":{"aliases":["GHSA-263v-6w9h-xf97"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Telegram mobile app","requires_auth":"none","summary":"Attackers can discover private phone numbers of Telegram users despite privacy settings by exploiting group information features.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"telegram","vendor":"telegram"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[],"description":"The Privacy \u003e Phone Number feature in the Telegram app 5.10 for Android and iOS provides an incorrect indication that the access level is Nobody, because attackers can find these numbers via the Group Info feature, e.g., by adding a significant fraction of a region's assigned phone numbers.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2021-12-21","github_poc":1,"max_poc_stars":26,"metasploit":0,"nuclei":0,"refs":[{"date":"2021-12-21T19:23:09Z","kind":"github_poc","ref":"https://github.com/bibi1959/CVE-2019-15514","stars":26,"title":"telegram bug that discloses user's hidden phone number (still unpatched) (exploit included) "}],"tier":"poc_unverified"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2019-15514","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2019-15515"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2019-15513"},"products":["n/a"],"published":"2019-08-23","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can discover private phone numbers of Telegram users despite privacy settings by exploiting group information features.","url":"https://insights.sbomify.com/CVE-2019-15514/"}