CVE-2014-5107: Infoleak

Published Jul 28, 2014

Updated

concrete5 before 5.6.3 allows remote attackers to obtain the installation path via a direct request to (1) system/basics/editor.php, (2) system/view.php, (3) system/environment/filestoragelocations.php, (4) system/mail/importers.php, (5) system/mail/method.php, (6) system/permissions/filetypes.php, (7) system/permissions/files.php, (8) system/permissions/tasks.php, (9) system/permissions/users.php, (10) system/seo/view.php, (11) view.php, (12) users/attributes.php, (13) scrapbook/view.php, (14) pages/attributes.php, (15) files/attributes.php, or (16) files/search.php in singlepages/dashboard/.

Affected Software

15 affected components

concrete5 concrete5=5.5.0

concrete5 concrete5=5.5.1

concrete5 concrete5=5.5.2

concrete5 concrete5=5.5.2.1

concrete5 concrete5=5.6.0

concrete5 concrete5=5.6.0.1

concrete5 concrete5=5.6.0.2

ConcreteCMS Concrete CMS=5.4.2

ConcreteCMS Concrete CMS=5.4.2.1

ConcreteCMS Concrete CMS=5.4.2.2

ConcreteCMS Concrete CMS=5.6.1

ConcreteCMS Concrete CMS=5.6.1.1

ConcreteCMS Concrete CMS=5.6.1.2

ConcreteCMS Concrete CMS=5.6.2

ConcreteCMS Concrete CMS=5.6.2.1

Event History

Jul 28, 2014

CVE Published

via MITRE·03:00 PM

Data Sourced

via MITRE·03:00 PM

Description

Frequently Asked Questions

What is the severity of CVE-2014-5107?

CVE-2014-5107 is considered to have a medium severity level due to its potential for information disclosure.

How do I fix CVE-2014-5107?

To fix CVE-2014-5107, upgrade to Concrete5 version 5.6.3 or later where the vulnerability has been addressed.

What versions of Concrete5 are affected by CVE-2014-5107?

CVE-2014-5107 affects Concrete5 versions from 5.5.0 to 5.6.2.1.

What type of attack does CVE-2014-5107 allow?

CVE-2014-5107 allows remote attackers to obtain the installation path through targeted HTTP requests.

Who is impacted by CVE-2014-5107?

Any Concrete5 users running affected versions prior to 5.6.3 are at risk due to CVE-2014-5107.