LiveActive security incident?Get immediate response
CVE Record

CVE-2017-13314: In setAllowOnlyVpnForUids of NetworkManagementService.java, there is a possible security settings bypass du...

In setAllowOnlyVpnForUids of NetworkManagementService.java, there is a possible security settings bypass due to a missing permission check. This could lead to local escalation of privilege allowing users to access non-VPN networks, when they are supposed to be restricted to the VPN networks, with no additional execution privileges needed. User interaction is not needed for exploitation.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Android flaw could let a local app or user bypass VPN-only network restrictions. For organizations relying on Android VPN enforcement to protect sensitive traffic, the business risk is data leaving the intended protected tunnel. The source bundle does not show active exploitation or public weaponization.

Executive priority

Prioritize remediation for enterprise Android fleets where VPN controls protect regulated, customer, or internal traffic. This is not internet-runnable, but it can undermine a core mobile data-protection control if affected devices remain in use.

Technical view

CVE-2017-13314 is a missing permission check in Android NetworkManagementService.setAllowOnlyVpnForUids. With local low privileges and no user interaction, an attacker could bypass security settings intended to restrict UIDs to VPN networks. The CVSS v3.1 score is 7.8 high, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on Android 7, 8, 8.1, and listed nyc-mr development branches that lack the relevant Google security bulletin fix. Risk is higher where enterprise policy depends on always-on or per-app VPN isolation.

Exploitation context

The provided sources describe local privilege escalation and VPN restriction bypass, requiring low privileges and no user interaction. KEV is false, and the bundle provides no evidence of active exploitation. Treat exploitation status as unconfirmed, not active.

Researcher notes

The source bundle identifies the vulnerable method, impact, affected Android versions, CVSS vector, and Google bulletin reference. It does not provide patch build identifiers, exploit samples, observed exploitation, or detailed detection telemetry. Avoid claiming active exploitation without additional cited evidence.

Mitigation direction

  • Review Google Android Security Bulletin 2018-05-01 for vendor fix guidance.
  • Update affected Android devices to supported patched builds.
  • Prioritize managed devices using always-on or per-app VPN controls.
  • Retire or isolate unsupported Android 7, 8, or 8.1 devices.
  • Verify MDM compliance policies require current Android security patch levels.

Validation and detection

  • Inventory Android device versions across managed and unmanaged fleets.
  • Compare device security patch levels with Google bulletin guidance.
  • Identify devices enforcing VPN-only or per-app VPN network controls.
  • Confirm unsupported affected versions are removed, isolated, or risk-accepted.
  • Review MDM reports for policy drift around VPN enforcement.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-276: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-13314 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2017-13314Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroid7, 8, 8.1, nyc-mr1-dev, nyc-mr2-devunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-276 · source CWE mapping

Incorrect Default Permissions

Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.