ID CVE-2015-8669
Summary libraries/config/messages.inc.php in phpMyAdmin 4.0.x before 4.0.10.12, 4.4.x before 4.4.15.2, and 4.5.x before 4.5.3.1 allows remote attackers to obtain sensitive information via a crafted request, which reveals the full path in an error message.
References
Vulnerable Configurations
  • phpMyAdmin 4.5.3
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.5.3
  • phpMyAdmin 4.5.2
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.5.2
  • phpMyAdmin 4.5.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.5.1
  • phpMYAdmin 4.5.0.2
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.5.0.2
  • phpMYAdmin 4.5.0.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.5.0.1
  • phpMYAdmin 4.5.0
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.5.0
  • phpMyAdmin 4.4.15.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.15.1
  • phpMYAdmin 4.4.15
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.15
  • phpMYAdmin 4.4.14.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.14.1
  • phpMyAdmin 4.4.13.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.13.1
  • phpMyAdmin 4.4.13
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.13
  • phpMyAdmin 4.4.12
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.12
  • phpMyAdmin 4.4.11
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.11
  • phpMyAdmin 4.4.10
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.10
  • phpMyAdmin 4.4.8
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.8
  • phpMyAdmin 4.4.9
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.9
  • phpMyAdmin 4.4.7
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.7
  • phpMyAdmin 4.4.6.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.6.1
  • phpMyAdmin 4.4.6
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.6
  • phpMyAdmin 4.4.5
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.5
  • phpMyAdmin 4.4.4
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.4
  • phpMyAdmin 4.4.3
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.3
  • phpMYAdmin 4.4.2
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.2
  • phpMyAdmin 4.4.1.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.1.1
  • phpMyAdmin 4.4.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.1
  • phpMyAdmin 4.4.0
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.4.0
  • phpMyAdmin 4.0.10.11
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.10.11
  • phpMyAdmin 4.0.10.10
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.10.10
  • phpMyAdmin 4.0.10.9
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.10.9
  • phpMyAdmin 4.0.10.8
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.10.8
  • phpMyAdmin 4.0.10.7
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.10.7
  • phpMyAdmin 4.0.10.6
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.10.6
  • phpMYAdmin 4.0.10.5
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.10.5
  • phpMYAdmin 4.0.10.2
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.10.2
  • phpMYAdmin 4.0.10
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.10
  • phpMyAdmin 4.0.10.4
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.10.4
  • phpMyAdmin 4.0.10.3
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.10.3
  • phpMyAdmin 4.0.10.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.10.1
  • phpMYAdmin 4.0.9
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.9
  • phpMYAdmin 4.0.8
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.8
  • phpMYAdmin 4.0.7
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.7
  • phpMYAdmin 4.0.6
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.6
  • phpMYAdmin 4.0.5
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.5
  • phpMYAdmin 4.0.4.2
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.4.2
  • phpMYAdmin 4.0.4.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.4.1
  • phpMYAdmin 4.0.4
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.4
  • phpMYAdmin 4.0.0
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.0
  • phpMYAdmin 4.0.3
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.3
  • phpMYAdmin 4.0.2
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.2
  • phpMYAdmin 4.0.1
    cpe:2.3:a:phpmyadmin:phpmyadmin:4.0.1
CVSS
Base: 5.0 (as of 28-12-2015 - 11:01)
Impact:
Exploitability:
CWE CWE-200
CAPEC
  • Subverting Environment Variable Values
    The attacker directly or indirectly modifies environment variables used by or controlling the target software. The attacker's goal is to cause the target software to deviate from its expected operation in a manner that benefits the attacker.
  • Footprinting
    An attacker engages in probing and exploration activity to identify constituents and properties of the target. Footprinting is a general term to describe a variety of information gathering techniques, often used by attackers in preparation for some attack. It consists of using tools to learn as much as possible about the composition, configuration, and security mechanisms of the targeted application, system or network. Information that might be collected during a footprinting effort could include open ports, applications and their versions, network topology, and similar information. While footprinting is not intended to be damaging (although certain activities, such as network scans, can sometimes cause disruptions to vulnerable applications inadvertently) it may often pave the way for more damaging attacks.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Browser Fingerprinting
    An attacker carefully crafts small snippets of Java Script to efficiently detect the type of browser the potential victim is using. Many web-based attacks need prior knowledge of the web browser including the version of browser to ensure successful exploitation of a vulnerability. Having this knowledge allows an attacker to target the victim with attacks that specifically exploit known or zero day weaknesses in the type and version of the browser used by the victim. Automating this process via Java Script as a part of the same delivery system used to exploit the browser is considered more efficient as the attacker can supply a browser fingerprinting method and integrate it with exploit code, all contained in Java Script and in response to the same web page request by the browser.
  • Session Credential Falsification through Prediction
    This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
  • Reusing Session IDs (aka Session Replay)
    This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.
  • Using Slashes in Alternate Encoding
    This attack targets the encoding of the Slash characters. An attacker would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the attacker many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL NONE NONE
nessus via4
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_88F75070ABCF11E583D36805CA0B3D42.NASL
    description The phpMyAdmin development team reports : By calling some scripts that are part of phpMyAdmin in an unexpected way, it is possible to trigger phpMyAdmin to display a PHP error message which contains the full path of the directory where phpMyAdmin is installed. We consider these vulnerabilities to be non-critical. This path disclosure is possible on servers where the recommended setting of the PHP configuration directive display_errors is set to on, which is against the recommendations given in the PHP manual for a production server.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 87614
    published 2015-12-29
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=87614
    title FreeBSD : phpMyAdmin -- path disclosure vulnerability (88f75070-abcf-11e5-83d3-6805ca0b3d42)
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2016-13.NASL
    description phpMyAdmin was updated to 4.4.15.2 to fix one security issue and one non-security bug. The following vulnerability was fixed : - CVE-2015-8669: It was possible to trigger phpMyAdmin to display a PHP error message which contains the full path of the directory where phpMyAdmin is installed (boo#960282) The following bug was fixed : - boo#960854: dependency of php-json was missing
    last seen 2019-02-21
    modified 2016-10-13
    plugin id 88114
    published 2016-01-25
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=88114
    title openSUSE Security Update : phpMyAdmin (openSUSE-2016-13)
refmap via4
confirm
sectrack 1034806
suse openSUSE-SU-2016:0067
Last major update 07-12-2016 - 13:29
Published 26-12-2015 - 17:59
Back to Top