{"id":"CVE-2017-15999","aliases":["EUVD-2017-7415","GHSA-vxjg-xmrq-x393"],"status":"published","title":"In the \"NQ Contacts Backup \u0026 Restore\" application 1.1 for Android, no HTTPS is used for...","description":"In the \"NQ Contacts Backup \u0026 Restore\" application 1.1 for Android, no HTTPS is used for transmitting login and synced user data. When logging in, the username is transmitted in cleartext along with an SHA-1 hash of the password. The attacker can either crack this hash or use it for further attacks where only the hash value is required.","severity":{"version":"3.0","score":9.8,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-09","score":0.00686,"percentile":0.52922,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-319"],"published":"2017-10-29T17:00:00Z","modified":"2026-06-17T01:08:37Z","products":[{"vendor":"nq","product":"contacts_backup_\\\u0026_restore"}],"references":[{"url":"https://1337sec.blogspot.de/2017/10/auditing-nq-contacts-backup-restore-11.html","tags":["x_refsource_MISC","x_transferred","Third Party Advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-15999"},{"url":"https://github.com/advisories/GHSA-vxjg-xmrq-x393"}],"sources":{"cve":[{"id":"CVE-2017-15999","description":"In the \"NQ Contacts Backup \u0026 Restore\" application 1.1 for Android, no HTTPS is used for transmitting login and synced user data. When logging in, the username is transmitted in cleartext along with an SHA-1 hash of the password. The attacker can either crack this hash or use it for further attacks where only the hash value is required.","status":"published","published":"2017-10-29T17:00:00Z","modified":"2024-09-16T18:43:44.967Z","updated_at":"2026-11-02T14:33:14.556599Z"}],"euvd":[{"id":"EUVD-2017-7415","description":"In the \"NQ Contacts Backup \u0026 Restore\" application 1.1 for Android, no HTTPS is used for transmitting login and synced user data. When logging in, the username is transmitted in cleartext along with an SHA-1 hash of the password. The attacker can either crack this hash or use it for further attacks where only the hash value is required.","status":"published","published":"2017-10-29T17:00:00Z","modified":"2024-09-16T18:43:44Z","updated_at":"2026-11-03T00:55:29.674428Z"}],"ghsa":[{"id":"GHSA-vxjg-xmrq-x393","title":"In the \"NQ Contacts Backup \u0026 Restore\" application 1.1 for Android, no HTTPS is used for...","description":"In the \"NQ Contacts Backup \u0026 Restore\" application 1.1 for Android, no HTTPS is used for transmitting login and synced user data. When logging in, the username is transmitted in cleartext along with an SHA-1 hash of the password. The attacker can either crack this hash or use it for further attacks where only the hash value is required.","status":"published","published":"2022-05-13T01:44:03Z","modified":"2023-02-02T05:01:04Z","cvss":[{"version":"3.0","score":9.8,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-319"],"updated_at":"2026-11-02T14:51:05.943235Z"}],"nvd":[{"id":"CVE-2017-15999","description":"In the \"NQ Contacts Backup \u0026 Restore\" application 1.1 for Android, no HTTPS is used for transmitting login and synced user data. When logging in, the username is transmitted in cleartext along with an SHA-1 hash of the password. The attacker can either crack this hash or use it for further attacks where only the hash value is required.","status":"published","published":"2017-10-29T17:29:00.313Z","modified":"2026-06-17T01:08:37.397Z","cvss":[{"version":"3.0","score":9.8,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"primary"},{"version":"2.0","score":5,"vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","level":"medium","assessor":"primary"}],"cwes":["CWE-319"],"updated_at":"2026-11-02T14:04:08.01771Z"}]}}