{"id":"CVE-2017-15999","state":"PUBLISHED","title":"In the \"NQ Contacts Backup & 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 cle","description":"In the \"NQ Contacts Backup & 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.","publishedAt":"2017-10-29T17:00:00.000Z","updatedAt":"2024-09-16T18:43:44.967Z","severity":null,"assigner":"mitre","products":["n/a n/a"],"affected":[{"vendor":"n/a","product":"n/a","versions":[{"version":"n/a","status":"affected"}]}],"references":["https://1337sec.blogspot.de/2017/10/auditing-nq-contacts-backup-restore-11.html"],"weaknesses":[],"ingestedAt":"2026-10-29T19:43:23.091Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2017/15xxx/CVE-2017-15999.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.1","cveMetadata":{"cveId":"CVE-2017-15999","state":"PUBLISHED","datePublished":"2017-10-29T17:00:00.000Z","dateUpdated":"2024-09-16T18:43:44.967Z","assignerShortName":"mitre","assignerOrgId":"8254265b-2729-46b6-b9e3-3dfca2d5bfca","dateReserved":"2017-10-29T00:00:00.000Z"},"containers":{"cna":{"descriptions":[{"lang":"en","value":"In the \"NQ Contacts Backup & 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."}],"affected":[{"vendor":"n/a","product":"n/a","versions":[{"version":"n/a","status":"affected"}]}],"references":[{"url":"https://1337sec.blogspot.de/2017/10/auditing-nq-contacts-backup-restore-11.html","tags":["x_refsource_MISC"]}],"problemTypes":[{"descriptions":[{"description":"n/a","lang":"en","type":"text"}]}],"providerMetadata":{"shortName":"mitre","dateUpdated":"2017-10-29T17:00:00.000Z","orgId":"8254265b-2729-46b6-b9e3-3dfca2d5bfca"},"x_legacyV4Record":{"CVE_data_meta":{"ASSIGNER":"cve@mitre.org","ID":"CVE-2017-15999","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"n/a","version":{"version_data":[{"version_value":"n/a"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"In the \"NQ Contacts Backup & 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."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"name":"https://1337sec.blogspot.de/2017/10/auditing-nq-contacts-backup-restore-11.html","refsource":"MISC","url":"https://1337sec.blogspot.de/2017/10/auditing-nq-contacts-backup-restore-11.html"}]}}},"adp":[{"title":"CVE Program Container","references":[{"url":"https://1337sec.blogspot.de/2017/10/auditing-nq-contacts-backup-restore-11.html","tags":["x_refsource_MISC","x_transferred"]}],"providerMetadata":{"shortName":"CVE","orgId":"af854a3a-2127-422b-91ae-364da2661108","dateUpdated":"2024-08-05T20:13:06.658Z"}}]}}}