CVE-2017-2748
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Isaac Mizrahi Smartwatch mobile app transmits login credentials over unencrypted HTTP instead of HTTPS, allowing man-in-the-middle attackers to intercept user credentials or session tokens during the authentication process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.2.10= 1.0.201601214= 1.2.2.12= 1.2.2016040820= 1.3.7= 1.3.2016052319= 1.4.8= 1.4.2016072601CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed app versionOpen the app's settings or the mobile device's app management interface to view the installed version number of the Isaac Mizrahi Smartwatch appAffected if The displayed version matches one of the affected versions: 1.0.2.10, 1.0.201601214, 1.2.2.12, 1.2.2016040820, 1.3.7, 1.3.2016052319, 1.4.8, or 1.4.2016072601
-
Capture network traffic during loginUse a network sniffer or proxy tool (such as Wireshark, Burp Suite, or Charles) to intercept network requests while performing a login operation in the app on a device connected through the proxyAffected if The login request is observed being sent to an HTTP (not HTTPS) URL, typically appearing as http:// rather than https:// in the captured traffic
-
Inspect app configuration for HTTP endpointsIf accessible, examine the app's configuration files, hardcoded endpoints, or decompiled source code for network request definitions to identify the protocol used for authentication endpointsAffected if Authentication-related URLs are configured to use HTTP (port 80) rather than HTTPS (port 443)
You are affected if the installed version matches any of the listed affected versions AND the app transmits login credentials over HTTP instead of HTTPS.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the app to use HTTPS for all login transactions with proper TLS/SSL certificate validation, ensuring all network communications are encrypted.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2748 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-2748 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data