ID CVE-2008-4578
Summary The ACL plugin in Dovecot before 1.1.4 allows attackers to bypass intended access restrictions by using the "k" right to create unauthorized "parent/child/child" mailboxes.
References
Vulnerable Configurations
  • cpe:2.3:a:dovecot:dovecot:0.99.13
    cpe:2.3:a:dovecot:dovecot:0.99.13
  • cpe:2.3:a:dovecot:dovecot:0.99.14
    cpe:2.3:a:dovecot:dovecot:0.99.14
  • cpe:2.3:a:dovecot:dovecot:1.0
    cpe:2.3:a:dovecot:dovecot:1.0
  • cpe:2.3:a:dovecot:dovecot:1.0.2
    cpe:2.3:a:dovecot:dovecot:1.0.2
  • cpe:2.3:a:dovecot:dovecot:1.0.3
    cpe:2.3:a:dovecot:dovecot:1.0.3
  • cpe:2.3:a:dovecot:dovecot:1.0.4
    cpe:2.3:a:dovecot:dovecot:1.0.4
  • cpe:2.3:a:dovecot:dovecot:1.0.5
    cpe:2.3:a:dovecot:dovecot:1.0.5
  • cpe:2.3:a:dovecot:dovecot:1.0.6
    cpe:2.3:a:dovecot:dovecot:1.0.6
  • cpe:2.3:a:dovecot:dovecot:1.0.7
    cpe:2.3:a:dovecot:dovecot:1.0.7
  • cpe:2.3:a:dovecot:dovecot:1.0.8
    cpe:2.3:a:dovecot:dovecot:1.0.8
  • cpe:2.3:a:dovecot:dovecot:1.0.9
    cpe:2.3:a:dovecot:dovecot:1.0.9
  • cpe:2.3:a:dovecot:dovecot:1.0.10
    cpe:2.3:a:dovecot:dovecot:1.0.10
  • cpe:2.3:a:dovecot:dovecot:1.0.12
    cpe:2.3:a:dovecot:dovecot:1.0.12
  • cpe:2.3:a:dovecot:dovecot:1.0.beta1
    cpe:2.3:a:dovecot:dovecot:1.0.beta1
  • cpe:2.3:a:dovecot:dovecot:1.0.beta2
    cpe:2.3:a:dovecot:dovecot:1.0.beta2
  • cpe:2.3:a:dovecot:dovecot:1.0.beta3
    cpe:2.3:a:dovecot:dovecot:1.0.beta3
  • cpe:2.3:a:dovecot:dovecot:1.0.beta4
    cpe:2.3:a:dovecot:dovecot:1.0.beta4
  • cpe:2.3:a:dovecot:dovecot:1.0.beta5
    cpe:2.3:a:dovecot:dovecot:1.0.beta5
  • cpe:2.3:a:dovecot:dovecot:1.0.beta6
    cpe:2.3:a:dovecot:dovecot:1.0.beta6
  • cpe:2.3:a:dovecot:dovecot:1.0.beta7
    cpe:2.3:a:dovecot:dovecot:1.0.beta7
  • cpe:2.3:a:dovecot:dovecot:1.0.beta8
    cpe:2.3:a:dovecot:dovecot:1.0.beta8
  • cpe:2.3:a:dovecot:dovecot:1.0.beta9
    cpe:2.3:a:dovecot:dovecot:1.0.beta9
  • cpe:2.3:a:dovecot:dovecot:1.0.rc1
    cpe:2.3:a:dovecot:dovecot:1.0.rc1
  • cpe:2.3:a:dovecot:dovecot:1.0.rc2
    cpe:2.3:a:dovecot:dovecot:1.0.rc2
  • cpe:2.3:a:dovecot:dovecot:1.0.rc3
    cpe:2.3:a:dovecot:dovecot:1.0.rc3
  • cpe:2.3:a:dovecot:dovecot:1.0.rc4
    cpe:2.3:a:dovecot:dovecot:1.0.rc4
  • cpe:2.3:a:dovecot:dovecot:1.0.rc5
    cpe:2.3:a:dovecot:dovecot:1.0.rc5
  • cpe:2.3:a:dovecot:dovecot:1.0.rc6
    cpe:2.3:a:dovecot:dovecot:1.0.rc6
  • cpe:2.3:a:dovecot:dovecot:1.0.rc7
    cpe:2.3:a:dovecot:dovecot:1.0.rc7
  • cpe:2.3:a:dovecot:dovecot:1.0.rc8
    cpe:2.3:a:dovecot:dovecot:1.0.rc8
  • cpe:2.3:a:dovecot:dovecot:1.0.rc9
    cpe:2.3:a:dovecot:dovecot:1.0.rc9
  • cpe:2.3:a:dovecot:dovecot:1.0.rc10
    cpe:2.3:a:dovecot:dovecot:1.0.rc10
  • cpe:2.3:a:dovecot:dovecot:1.0.rc11
    cpe:2.3:a:dovecot:dovecot:1.0.rc11
  • cpe:2.3:a:dovecot:dovecot:1.0.rc12
    cpe:2.3:a:dovecot:dovecot:1.0.rc12
  • cpe:2.3:a:dovecot:dovecot:1.0.rc13
    cpe:2.3:a:dovecot:dovecot:1.0.rc13
  • cpe:2.3:a:dovecot:dovecot:1.0.rc14
    cpe:2.3:a:dovecot:dovecot:1.0.rc14
  • cpe:2.3:a:dovecot:dovecot:1.0.rc15
    cpe:2.3:a:dovecot:dovecot:1.0.rc15
  • cpe:2.3:a:dovecot:dovecot:1.0.rc16
    cpe:2.3:a:dovecot:dovecot:1.0.rc16
  • cpe:2.3:a:dovecot:dovecot:1.0.rc17
    cpe:2.3:a:dovecot:dovecot:1.0.rc17
  • cpe:2.3:a:dovecot:dovecot:1.0.rc18
    cpe:2.3:a:dovecot:dovecot:1.0.rc18
  • cpe:2.3:a:dovecot:dovecot:1.0.rc19
    cpe:2.3:a:dovecot:dovecot:1.0.rc19
  • cpe:2.3:a:dovecot:dovecot:1.0.rc20
    cpe:2.3:a:dovecot:dovecot:1.0.rc20
  • cpe:2.3:a:dovecot:dovecot:1.0.rc21
    cpe:2.3:a:dovecot:dovecot:1.0.rc21
  • cpe:2.3:a:dovecot:dovecot:1.0.rc22
    cpe:2.3:a:dovecot:dovecot:1.0.rc22
  • cpe:2.3:a:dovecot:dovecot:1.0.rc23
    cpe:2.3:a:dovecot:dovecot:1.0.rc23
  • cpe:2.3:a:dovecot:dovecot:1.0.rc24
    cpe:2.3:a:dovecot:dovecot:1.0.rc24
  • cpe:2.3:a:dovecot:dovecot:1.0.rc25
    cpe:2.3:a:dovecot:dovecot:1.0.rc25
  • cpe:2.3:a:dovecot:dovecot:1.0.rc26
    cpe:2.3:a:dovecot:dovecot:1.0.rc26
  • cpe:2.3:a:dovecot:dovecot:1.0.rc27
    cpe:2.3:a:dovecot:dovecot:1.0.rc27
  • cpe:2.3:a:dovecot:dovecot:1.0.rc28
    cpe:2.3:a:dovecot:dovecot:1.0.rc28
  • cpe:2.3:a:dovecot:dovecot:1.0_rc29
    cpe:2.3:a:dovecot:dovecot:1.0_rc29
  • cpe:2.3:a:dovecot:dovecot:1.1
    cpe:2.3:a:dovecot:dovecot:1.1
  • cpe:2.3:a:dovecot:dovecot:1.1:rc2
    cpe:2.3:a:dovecot:dovecot:1.1:rc2
  • cpe:2.3:a:dovecot:dovecot:1.1.0
    cpe:2.3:a:dovecot:dovecot:1.1.0
  • cpe:2.3:a:dovecot:dovecot:1.1.1
    cpe:2.3:a:dovecot:dovecot:1.1.1
  • cpe:2.3:a:dovecot:dovecot:1.1.2
    cpe:2.3:a:dovecot:dovecot:1.1.2
  • cpe:2.3:a:dovecot:dovecot:1.1.3
    cpe:2.3:a:dovecot:dovecot:1.1.3
CVSS
Base: 5.0 (as of 16-10-2008 - 10:49)
Impact:
Exploitability:
CWE CWE-264
CAPEC
  • Accessing, Modifying or Executing Executable Files
    An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
  • Leverage Executable Code in Non-Executable Files
    An attack of this type exploits a system's trust in configuration and resource files, when the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high. The attack can be directed at a client system, such as causing buffer overrun through loading seemingly benign image files, as in Microsoft Security Bulletin MS04-028 where specially crafted JPEG files could cause a buffer overrun once loaded into the browser. Another example targets clients reading pdf files. In this case the attacker simply appends javascript to the end of a legitimate url for a pdf (http://www.gnucitizen.org/blog/danger-danger-danger/) http://path/to/pdf/file.pdf#whatever_name_you_want=javascript:your_code_here The client assumes that they are reading a pdf, but the attacker has modified the resource and loaded executable javascript into the client's browser process. The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name "public" grants all users with the public role the ability to use the administration functionality. The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.
  • Blue Boxing
    This type of attack against older telephone switches and trunks has been around for decades. A tone is sent by an adversary to impersonate a supervisor signal which has the effect of rerouting or usurping command of the line. While the US infrastructure proper may not contain widespread vulnerabilities to this type of attack, many companies are connected globally through call centers and business process outsourcing. These international systems may be operated in countries which have not upgraded Telco infrastructure and so are vulnerable to Blue boxing. Blue boxing is a result of failure on the part of the system to enforce strong authorization for administrative functions. While the infrastructure is different than standard current applications like web applications, there are historical lessons to be learned to upgrade the access control for administrative functions.
  • Restful Privilege Elevation
    Rest uses standard HTTP (Get, Put, Delete) style permissions methods, but these are not necessarily correlated generally with back end programs. Strict interpretation of HTTP get methods means that these HTTP Get services should not be used to delete information on the server, but there is no access control mechanism to back up this logic. This means that unless the services are properly ACL'd and the application's service implementation are following these guidelines then an HTTP request can easily execute a delete or update on the server side. The attacker identifies a HTTP Get URL such as http://victimsite/updateOrder, which calls out to a program to update orders on a database or other resource. The URL is not idempotent so the request can be submitted multiple times by the attacker, additionally, the attacker may be able to exploit the URL published as a Get method that actually performs updates (instead of merely retrieving data). This may result in malicious or inadvertent altering of data on the server.
  • Target Programs with Elevated Privileges
    This attack targets programs running with elevated privileges. The attacker would try to leverage a bug in the running program and get arbitrary code to execute with elevated privileges. For instance an attacker would look for programs that write to the system directories or registry keys (such as HKLM, which stores a number of critical Windows environment variables). These programs are typically running with elevated privileges and have usually not been designed with security in mind. Such programs are excellent exploit targets because they yield lots of power when they break. The malicious user try to execute its code at the same level as a privileged system call.
  • Manipulating Input to File System Calls
    An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
NONE PARTIAL NONE
nessus via4
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_75C24C1DB68811DD88FD001C2514716C.NASL
    description Timo Sirainen reports in dovecot 1.1.4 release notes : ACL plugin fixes: Negative rights were actually treated as positive rights. 'k' right didn't prevent creating parent/child/child mailbox. ACL groups weren't working.
    last seen 2019-02-21
    modified 2018-12-05
    plugin id 34838
    published 2008-11-21
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=34838
    title FreeBSD : dovecot -- ACL plugin bypass vulnerabilities (75c24c1d-b688-11dd-88fd-001c2514716c)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-200812-16.NASL
    description The remote host is affected by the vulnerability described in GLSA-200812-16 (Dovecot: Multiple vulnerabilities) Several vulnerabilities were found in Dovecot: The 'k' right in the acl_plugin does not work as expected (CVE-2008-4577, CVE-2008-4578) The dovecot.conf is world-readable, providing improper protection for the ssl_key_password setting (CVE-2008-4870) A permanent Denial of Service with broken mail headers is possible (CVE-2008-4907) Impact : These vulnerabilities might allow a remote attacker to cause a Denial of Service, to circumvent security restrictions or allow local attackers to disclose the passphrase of the SSL private key. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-12-05
    plugin id 35108
    published 2008-12-15
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=35108
    title GLSA-200812-16 : Dovecot: Multiple vulnerabilities
  • NASL family Mandriva Local Security Checks
    NASL id MANDRIVA_MDVSA-2008-232.NASL
    description The ACL plugin in dovecot prior to version 1.1.4 treated negative access rights as though they were positive access rights, which allowed attackers to bypass intended access restrictions (CVE-2008-4577). The ACL plugin in dovecot prior to version 1.1.4 allowed attackers to bypass intended access restrictions by using the 'k' right to create unauthorized 'parent/child/child' mailboxes (CVE-2008-4578). In addition, two bugs were discovered in the dovecot package shipped with Mandriva Linux 2009.0. The default permissions on the dovecot.conf configuration file were too restrictive, which prevents the use of dovecot's 'deliver' command as a non-root user. Secondly, dovecot should not start until after ntpd, if ntpd is active, because if ntpd corrects the time backwards while dovecot is running, dovecot will quit automatically, with the log message 'Time just moved backwards by X seconds. This might cause a lot of problems, so I'll just kill myself now.' The update resolves both these problems. The default permissions on dovecot.conf now allow the 'deliver' command to read the file. Note that if you edited dovecot.conf at all prior to installing the update, the new permissions may not be applied. If you find the 'deliver' command still does not work following the update, please run these commands as root : # chmod 0640 /etc/dovecot.conf # chown root:mail /etc/dovecot.conf Dovecot's initialization script now configures it to start after the ntpd service, to ensure ntpd resetting the clock does not interfere with Dovecot operation. This package corrects the above-noted bugs and security issues by upgrading to the latest dovecot 1.1.6, which also provides additional bug fixes.
    last seen 2019-02-21
    modified 2018-07-19
    plugin id 38066
    published 2009-04-23
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=38066
    title Mandriva Linux Security Advisory : dovecot (MDVSA-2008:232)
refmap via4
bid 31587
bugtraq 20081119 Re: [ MDVSA-2008:232 ] dovecot
confirm http://bugs.gentoo.org/show_bug.cgi?id=240409
gentoo GLSA-200812-16
mandriva MDVSA-2008:232
mlist [Dovecot-news] 20081005 v1.1.4 released
secunia
  • 32164
  • 33149
vupen ADV-2008-2745
xf dovecot-acl-mailbox-security-bypass(45669)
statements via4
contributor Joshua Bressers
lastmodified 2008-10-24
organization Red Hat
statement The risks associated with fixing this bug are greater than the low severity security risk. We therefore currently have no plans to fix this flaw in Red Hat Enterprise Linux 5.
Last major update 07-03-2011 - 22:12
Published 15-10-2008 - 16:08
Last modified 11-10-2018 - 16:52
Back to Top