Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2016-3757

The print_maps function in toolbox/lsof.c in Android 4.x before 4.4.4, 5.0.x before 5.0.2, 5.1.x before 5.1.1, and 6.x before 2016-07-01 allows user-assisted attackers to gain privileges via a crafted application that attempts to list a long name of a memory-mapped file, aka internal bug 28175237. NOTE: print_maps is not related to the Vic Abell lsof product.

Security Impact Summary

This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 7.0, requiring local system access to exploit but requires specific conditions to be met without requiring user interaction requiring only low-level privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 1 product from google organizations running these solutions should prioritize assessment and patching.

Historical Context

First disclosed in 2016, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.

Published

2016-07-11T01:59:57.980

Last Modified

2025-04-12T10:46:40.837

Status

Deferred

Source

[email protected]

Severity

CVSSv3.0: 7.0 (HIGH)

CVSSv2 Vector

AV:L/AC:M/Au:N/C:P/I:P/A:C

Access Vector: LOCAL
Access Complexity: MEDIUM
Authentication: NONE
Confidentiality Impact: PARTIAL
Integrity Impact: PARTIAL
Availability Impact: COMPLETE

Exploitability Score

3.4

Impact Score

8.5

Weaknesses

Type: Primary
CWE-20

Affected Vendors & Products

Type	Vendor	Product	Version/Range	Vulnerable?
Operating System	google	android	4.0	Yes
Operating System	google	android	4.0.1	Yes
Operating System	google	android	4.0.2	Yes
Operating System	google	android	4.0.3	Yes
Operating System	google	android	4.0.4	Yes
Operating System	google	android	4.1	Yes
Operating System	google	android	4.1.2	Yes
Operating System	google	android	4.2	Yes
Operating System	google	android	4.2.1	Yes
Operating System	google	android	4.2.2	Yes
Operating System	google	android	4.3	Yes
Operating System	google	android	4.3.1	Yes
Operating System	google	android	4.4	Yes
Operating System	google	android	4.4.1	Yes
Operating System	google	android	4.4.2	Yes
Operating System	google	android	4.4.3	Yes
Operating System	google	android	5.0	Yes
Operating System	google	android	5.0.1	Yes
Operating System	google	android	5.1	Yes
Operating System	google	android	5.1.0	Yes
Operating System	google	android	6.0	Yes
Operating System	google	android	6.0.1	Yes

References

http://source.android.com/security/bulletin/2016-07-01.html Vendor Advisory ([email protected])
https://android.googlesource.com/platform/system/core/+/ae18eb014609948a40e22192b87b10efc680daa7 ([email protected])
http://source.android.com/security/bulletin/2016-07-01.html Vendor Advisory (af854a3a-2127-422b-91ae-364da2661108)
https://android.googlesource.com/platform/system/core/+/ae18eb014609948a40e22192b87b10efc680daa7 (af854a3a-2127-422b-91ae-364da2661108)

How SecUtils Interprets This CVE

SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For google's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.