CVE-2012-5665: Medium severity owncloud vulnerability
Published Jan 3, 2013
·Updated
ownCloud 4.0.x before 4.0.10 and 4.5.x before 4.5.5 does not properly restrict access to settings.php, which allows remote attackers to edit app configurations of userwebdavauth and userldap by editing this file.
Affected Software
30 affected components
ownCloud ownCloud=4.0.0
ownCloud ownCloud=4.0.1
ownCloud ownCloud=4.0.2
ownCloud ownCloud=4.0.3
ownCloud ownCloud=4.0.4
ownCloud ownCloud=4.0.5
ownCloud ownCloud=4.0.6
ownCloud ownCloud=4.0.7
ownCloud ownCloud=4.0.8
ownCloud ownCloud=4.0.9
ownCloud ownCloud=4.5.0
ownCloud ownCloud=4.5.1
ownCloud ownCloud=4.5.2
ownCloud ownCloud=4.5.3
ownCloud ownCloud=4.5.4
ownCloud ownCloud Server=4.0.0
ownCloud ownCloud Server=4.0.1
ownCloud ownCloud Server=4.0.2
ownCloud ownCloud Server=4.0.3
ownCloud ownCloud Server=4.0.4
ownCloud ownCloud Server=4.0.5
ownCloud ownCloud Server=4.0.6
ownCloud ownCloud Server=4.0.7
ownCloud ownCloud Server=4.0.8
ownCloud ownCloud Server=4.0.9
ownCloud ownCloud Server=4.5.0
ownCloud ownCloud Server=4.5.1
ownCloud ownCloud Server=4.5.2
ownCloud ownCloud Server=4.5.3
ownCloud ownCloud Server=4.5.4
Remediation
Patch Available
Patch Available
Event History
Jan 3, 2013
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description
Data Sourced
via NVD·01:55 AM
RemedyDescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2012-5665?
CVE-2012-5665 has a medium severity level, as it allows unauthorized edits to critical configuration files.
2
How do I fix CVE-2012-5665?
To resolve CVE-2012-5665, you should update ownCloud to version 4.0.10, 4.5.5, or later.
3
What versions of ownCloud are affected by CVE-2012-5665?
CVE-2012-5665 affects ownCloud versions 4.0.x prior to 4.0.10 and 4.5.x prior to 4.5.5.
4
What can attackers do with CVE-2012-5665?
Attackers can remotely edit important app configurations by accessing the settings.php file, leading to potential data breaches.
5
Is there a workaround for CVE-2012-5665?
There are no known workarounds for CVE-2012-5665; upgrading to a patched version is the recommended action.