BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2018
CVE-2017-14878High confidence

Affected product: Improper Input Validation

Unknown · Unknown

7.5HighCVSS 3.0
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 1.11% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2017-6356

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

In Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux kernel, a length variable which is used to copy data has a size of only 8 bits and can be exceeded resulting in a denial of service.

What

In Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux kernel, a length variable which is used to copy data has a size of only 8 bits and can be exceeded resulting in a denial of service.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

In Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux kernel, a length variable which is used to copy data has a size of only 8 bits and can be exceeded resulting in a denial of service.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Input Validation → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-20 ↗

CWE-20: Improper Input Validation. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedDenial of serviceCWE-20
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Canadian Centre for Cyber Security · English · AV18-057Android security bulletin – March 2018

Number: AV18-057 Date: 06 April 2018 Purpose The purpose of this advisory is to bring attention to the Android Security Bulletin for March 2018. Assessment The Android Security Bulletin addresses security updates for multiple vulnerabilities. Successful exploitation could result in remote code execution. CVE References: CVE-2016-10393, CVE-2017-13248, CVE-2017-13249, CVE-2017-13250, CVE-2017-13251, CVE-2017-13252, CVE-2017-13253, CVE-2017-14878, CVE-2017-14882, CVE-2017-14885, CVE-2017-15815, CVE-2017-15821, CVE-2017-16525, CVE-2017-16529, CVE-2017-16530, CVE-2017-16531, CVE-2017-16533, CVE-2017-16535, CVE-2017-17773, CVE-2017-18056, CVE-2017-18063, CVE-2017-18064, CVE-2017-18067, CVE-2017-18068, CVE-2017-18069, CVE-2017-6281, CVE-2017-6286 Suggested action CCIRC recommends that system administrators test and deploy the vendor-released updates to affected applications accordingly. References https://source.android.com/security/bulletin/2018-03-01

Official advisory ↗
CERT-FR · French · CERTFR-2018-AVI-112Multiples vulnérabilités dans Google Android

d?id=CVE-2017-13263 Référence CVE CVE-2017-13264 https://www.cve.org/CVERecord?id=CVE-2017-13264 Référence CVE CVE-2017-13265 https://www.cve.org/CVERecord?id=CVE-2017-13265 Référence CVE CVE-2017-13266 https://www.cve.org/CVERecord?id=CVE-2017-13266 Référence CVE CVE-2017-13268 https://www.cve.org/CVERecord?id=CVE-2017-13268 Référence CVE CVE-2017-13269 https://www.cve.org/CVERecord?id=CVE-2017-13269 Référence CVE CVE-2017-13270 https://www.cve.org/CVERecord?id=CVE-2017-13270 Référence CVE CVE-2017-13271 https://www.cve.org/CVERecord?id=CVE-2017-13271 Référence CVE CVE-2017-13272 https://www.cve.org/CVERecord?id=CVE-2017-13272 Référence CVE CVE-2017-14878 https://www.cve.org/CVERecord?id=CVE-2017-14878 Référence CVE CVE-2017-14879 https://www.cve.org/CVERecord?id=CVE-2017-14879 Référence CVE CVE-2017-14882 https://www.cve.org/CVERecord?id=CVE-2017-14882 Référence CVE CVE-2017-14885 https://www.cve.org/CVERecord?id=CVE-2017-14885 Référence CVE CVE-2017-14887 https://www.cve.org/CVERecord?id=CVE-2017-14887 Référence CVE CVE-2017-14889 https://www.cve.org/CVERecord?id=CVE-2017-14889 Référence CVE CVE-2017-15649 https://www.cve.org/CVERecord?id=CVE-2017-15649 Référence CVE CVE-2017-15814 https://www.cve.org/CVERecord?id=CVE-2017-15814 Référence CVE CVE-2017-15815 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2017-012944Android における入力確認に関する脆弱性

Android には、入力確認に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
n/a
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 15 Mar 2018 · Last source change 5 Aug 2024, 19:42 UTC · CWE-20 · Improper Input Validation

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-09-01
European sourceENISA EUVD · EUVD-2017-6356
Product sourceUnavailable
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. ENISA EUVD mappingEUVD-2017-6356 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2017-6356"}
    ENISA EUVD ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added patch: source.codeaurora.org/commit?id=27f1c544d6737bcb3dc4bb114badcd47ce946a8b; added remediation: source.codeaurora.org/commit?id=27f1c544d6737bcb3dc4bb114badcd47ce946a8b; 1 further additions.
    Before
    no authoritative guidance recorded
    After
    patch: source.codeaurora.org/commit?id=27f1c544d6737bcb3dc4bb114badcd47ce946a8b · remediation: source.codeaurora.org/commit?id=27f1c544d6737bcb3dc4bb114badcd47ce946a8b · vendor advisory: source.android.com/2018-03-01
    source.codeaurora.org ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    n/a · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    n/a · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
  4. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    source.codeaurora.org ↗
  5. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    NIST NVD ↗
  6. CVSS scoreCVSS score changed from not recorded to 7.5 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
    Before
    not recorded
    After
    7.5 (CVSS 3.0 · NIST NVD · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
    NIST NVD ↗
  7. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2017-6356↗CVE authority or vendor reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2017-14878 · cve.blacktree.nl