RCBlog insecure data and config directories

rcblog-data-config-insecure-directories (24249) The risk level is classified as MediumMedium Risk

Description:

RCBlog could allow a remote attacker to obtain sensitive information. The default installation of RCBlog fails to protect the data and config directories in htaccess. A remote attacker could view these files and obtain valid usernames and password hashes, which could be used to gain unauthorized access to the application.


Consequences:

Obtain Information

Remedy:

RCBlog is no longer supported and has been replaced with the FLog software. Upgrade to the current version of FLog (version 1.1.2 or later) available from the Fluffington.com Web site. See References.

References:

  • eVuln Advisory EV0042: RCBlog Directory Traversal & Sensitive Information Disclosure.
  • Fluffington.com Web site: FLog - Download page.
  • Fluffington.com Web site: RCBlog - Download page.
  • CVE-2006-0370: Noah Medling RCBlog 1.03 stores the data and config directories under the web root with insufficient access control, which allows remote attackers to view account names and MD5 password hashes.
  • OSVDB ID: 22679: RCBlog data Directory Direct Access User Account Information Disclosure
  • OSVDB ID: 51465: RCBlog config/password.txt Direct Request Admin Credentials Hash Disclosure
  • SA18547: RCBlog File Upload and Disclosure of Sensitive Information
  • SA33584: RCBlog "password.txt" Information Disclosure Security Issue
  • SECTRACK ID: 1015523: RCBlog Input Validation Hole Lets Remote Users Traverse the Directory

Platforms Affected:

  • Noah Medling RCBlog 1.03

Reported:

Jan 19, 2006

The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.

For corrections or additions please email ignore thisxforceignore this@ignore thisus.ignore thisibm.comignore this

Return to the main page