dbcve.org
P7 FirmwareOperating system · Huawei

CVE-2015-8304

HIGH · 7.8 CVSS v3.0 Published 2016-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Integer overflow in Huawei P7 phones with software before P7-L07 V100R001C01B606 allows remote attackers to gain privileges via a crafted application with the system or camera permission.

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 confidence

Integer overflow vulnerability in Huawei P7 Android phones prior to software version P7-L07 V100R001C01B606 allows a malicious application possessing system or camera permissions to trigger the overflow and escalate privileges, potentially executing arbitrary code with elevated access.

MitigationUpdate Huawei P7 devices to software version P7-L07 V100R001C01B606 or later to obtain the vendor patch addressing the integer overflow.

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
P7 FirmwareOperating system
Affected:<= p7-l07_v100r001c01b606

CVSS 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is Huawei P7
    Check the device model in Settings > About Phone > Model Number, or look for P7-L07 or similar P7 variant in the device specifications
    Affected if Device is a Huawei P7 (P7-L07 or related P7 model)
  2. Locate software version information
    Navigate to Settings > About Phone on the Huawei P7 device and locate the Version, Software Version, or Firmware Version field
    Affected if Version information is accessible in device settings
  3. Compare installed version to affected range
    Compare the displayed software version against the affected range: any version <= P7-L07 V100R001C01B606 is vulnerable
    Affected if Software version is P7-L07 V100R001C01B606 or any earlier version (numerically lower)
  4. Check build number if available
    In Settings > About Phone > Build Number, verify the build identifier - earlier builds before the B606 patch level indicate the vulnerable version
    Affected if Build number corresponds to a version earlier than B606

A user is affected if they own a Huawei P7 device running software version P7-L07 V100R001C01B606 or any earlier version, as the integer overflow vulnerability exists in those firmware releases.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Huawei P7 devices to software version P7-L07 V100R001C01B606 or later to obtain the vendor patch addressing the integer overflow.

Fix this in P7 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-8304 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-8304 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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