Skip to content
Noroxi
CVE-2017-3760· NVD / CVE Program· CNA lenovo

The Lenovo Service Framework Android application uses a set of nonsecure credentials when performing integrity verification of downloaded ap

The Lenovo Service Framework Android application uses a set of nonsecure credentials when performing integrity verification of downloaded applications and/or data. This exposes the application to man-in-the-middle attacks leading to possible remote code execution.

HighCVSS 8.1 · v3.0—No exploit No fix recorded

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help
Published
Oct 17, 2017
Updated
Jun 16, 2026
EPSS
0.8% · 54th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

32

Monitor

Low priority for now.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.8%

Affected systems

VendorProduct
lenovoservice framework

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • lenovo service frameworkall versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (lenovo). Independent of NVD's CPE analysis and usually ahead of it.

  • Lenovo Group Ltd. Service Framework application

    • various versionsaffected

Same product

lenovo: all records

Other highest-scoring records for the same primary product.

  • CVE-2017-3761The Lenovo Service Framework Android application executes some system commands without proper sanitization of external input.
    40Plan
  • CVE-2017-3758Improper access controls on several Android components in the Lenovo Service Framework application can be exploited to enable remote code ex
    40Plan
  • CVE-2017-3759The Lenovo Service Framework Android application accepts some responses from the server without proper validation.
    33Monitor
  • CVE-2024-33582A DLL hijack vulnerability was reported in Lenovo Service Framework that could allow a local attacker to execute code with elevated privileg
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-354 · Improper Validation of Integrity Check Value

CVSS vector

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records