VDB-91050 · CVE-2016-6398 · BID 92734

Cisco IOS Point-to-Point Tunneling Protocol Server Memory information disclosure

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.2$0-$5k0.00

Summaryinfo

A vulnerability categorized as problematic has been discovered in Cisco IOS. This vulnerability affects unknown code of the component Point-to-Point Tunneling Protocol Server. The manipulation results in information disclosure (Memory). This vulnerability is known as CVE-2016-6398. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Cisco IOS (Router Operating System) (affected version unknown). It has been classified as problematic. Affected is an unknown functionality of the component Point-to-Point Tunneling Protocol Server. The manipulation with an unknown input leads to a information disclosure vulnerability (Memory). CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. CVE summarizes:

The PPTP server in Cisco IOS 15.5(3)M does not properly initialize packet buffers, which allows remote attackers to obtain sensitive information from earlier network communication by reading packet data, aka Bug ID CSCvb16274.

The weakness was published 09/02/2016 with Cisco as cisco-sa-20160902-ios as confirmed advisory (Website). The advisory is available at tools.cisco.com. This vulnerability is traded as CVE-2016-6398 since 07/26/2016. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1592 by the MITRE ATT&CK project. The advisory points out:

The vulnerability is due to the use of a previously used packet buffer whose content was not cleared from memory. An attacker could exploit this vulnerability by sending a PPTP connection request to device that is running a vulnerable release of the affected software and is configured for PPTP server functionality. A successful exploit could allow the attacker to access up to 63 bytes of memory that were previously used for a packet and were either destined to the device or generated by the device. An exploit would not allow the attacker to access packet data from transit traffic. In addition, an exploit would not allow the attacker to access arbitrary memory locations that the attacker chooses.

Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability. The advisory contains the following remark:

To work around this vulnerability, administrators can configure a 64-character local name for any virtual private dialup network (VPDN) group that is enabled for PPTP functionality. This will prevent content from being leaked from memory. The local name must be exactly 64 characters in length.

The vulnerability is also documented in the databases at SecurityFocus (BID 92734†) and SecurityTracker (ID 1036732†). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.2

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.3
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Name: Memory
Class: Information disclosure / Memory
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

OpenVAS ID: 103403
OpenVAS Name: Cisco IOS Software Point-to-Point Tunneling Protocol Server Information Disclosure Vulnerability
OpenVAS File: 🔍
OpenVAS Family: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

07/26/2016 🔍
09/02/2016 +38 days 🔍
09/02/2016 +0 days 🔍
09/02/2016 +0 days 🔍
09/03/2016 +1 days 🔍
09/06/2016 +3 days 🔍
09/12/2016 +6 days 🔍
09/14/2022 +2193 days 🔍

Sourcesinfo

Vendor: cisco.com

Advisory: cisco-sa-20160902-ios
Organization: Cisco
Status: Confirmed

CVE: CVE-2016-6398 (🔍)
GCVE (CVE): GCVE-0-2016-6398
GCVE (VulDB): GCVE-100-91050

OVAL: 🔍

SecurityFocus: 92734 - Cisco IOS CVE-2016-6398 Information Disclosure Vulnerability
SecurityTracker: 1036732

Entryinfo

Created: 09/03/2016 17:58
Updated: 09/14/2022 16:20
Changes: 09/03/2016 17:58 (58), 04/10/2019 22:37 (11), 09/14/2022 16:20 (12)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!