{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-18800 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-18800 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-18800 is a high-severity vulnerability in n/a, published on 6 Nov 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-18800 and fix it if it is affected.\n\nWhat it is: CVE-2019-18800 is a high-severity vulnerability in n/a, published on 6 Nov 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-18800 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-18800/ (Markdown: https://insights.sbomify.com/CVE-2019-18800/index.md)","id":"CVE-2019-18800","markdown":"https://insights.sbomify.com/CVE-2019-18800/index.md","name":"CVE-2019-18800","record":{"aliases":["GHSA-h624-wrj8-hr3r"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Viber mobile app","requires_auth":"none","summary":"Remote attackers can steal Viber accounts by intercepting unencrypted traffic to extract device identifiers and replaying them during registration.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"viber","vendor":"rakuten"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"},{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"Viber through 11.7.0.5 allows a remote attacker who can capture a victim's internet traffic to steal their Viber account, because not all Viber protocol traffic is encrypted. TCP data packet 9 on port 4244 from the victim's device contains cleartext information such as the device model and OS version, IMSI, and 20 bytes of udid in a binary format, which is located at offset 0x14 of this packet. Then, the attacker installs Viber on his device, initiates the registration process for any phone number, but doesn't enter a pin from SMS. Instead, he closes Viber. Next, the attacker rewrites his udid with the victim's udid, modifying the viber_udid file, which is located in the Viber preferences folder. (The udid is stored in a hexadecimal format.) Finally, the attacker starts Viber again and enters the pin from SMS.","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":"Information disclosure in n/a","id":"CVE-2019-18800","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":"Memory corruption in n/a","id":"CVE-2019-18801"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2019-18799"},"products":["n/a"],"published":"2019-11-06","related":[{"cvss_score":9.8,"headline":"Rakuten Viber uses broken or risky cryptographic Algorithm","id":"CVE-2025-13476","kev_date_added":null,"published":"2026-03-05"},{"cvss_score":7.8,"headline":"Path traversal in n/a","id":"CVE-2019-12569","kev_date_added":null,"published":"2019-06-03"},{"cvss_score":7.5,"headline":"Other in n/a","id":"CVE-2020-14049","kev_date_added":null,"published":"2020-06-22"},{"cvss_score":6.3,"headline":"Cross-site scripting in n/a","id":"CVE-2025-55996","kev_date_added":null,"published":"2025-09-12"},{"cvss_score":4.2,"headline":"Information disclosure in Rakuten Viber","id":"CVE-2018-3987","kev_date_added":null,"published":"2020-02-12"}],"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-05","vendors":["n/a"]},"summary":"Remote attackers can steal Viber accounts by intercepting unencrypted traffic to extract device identifiers and replaying them during registration.","url":"https://insights.sbomify.com/CVE-2019-18800/"}