# CVE-2017-2748: Weak cryptography in Isaac Mizrahi Smartwatch Mobile App

> Attackers can intercept login credentials due to insecure HTTP transactions in the Isaac Mizrahi Smartwatch mobile app.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vv6v-7j34-7w7m

## What is CVE-2017-2748?

CVE-2017-2748 is a high-severity vulnerability in Isaac Mizrahi Smartwatch Mobile App, published on 27 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A potential security vulnerability caused by the use of insecure (http) transactions during login has been identified with early versions of the Isaac Mizrahi Smartwatch mobile app. HP has no access to customer data as a result of this issue.

Weakness: CWE-254

## Which versions are affected by CVE-2017-2748?

It affects 1 product.


Products: Hp Isaac Mizrahi Smartwatch.

## How do I fix CVE-2017-2748?

No fix has been published for CVE-2017-2748 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-2748 being exploited?

There is no known exploitation of CVE-2017-2748 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-2748 and fix it if it is affected.

What it is: CVE-2017-2748 is a high-severity vulnerability in Isaac Mizrahi Smartwatch Mobile App, published on 27 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-2748 in the wild and no public exploit code.

Affected product: Isaac Mizrahi Smartwatch Mobile App. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-2748/ (Markdown: https://insights.sbomify.com/CVE-2017-2748/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-2748
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-2748
- OSV: https://osv.dev/vulnerability/CVE-2017-2748

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-2748/
Summaries are generated and may contain mistakes; the official description above is the record.