|
Debian "apt-setup" Insecure File Permission Security Issue
|
|
|
|
|
Secunia Advisory:
|
SA15955
|
|
|
Release Date:
|
2005-07-07
|
|
Last Update:
|
2006-01-31
|
|
|
Critical:
|
Less critical
|
|
Impact:
|
Exposure of sensitive information
|
|
Where:
|
Local system
|
|
Solution Status:
|
Unpatched
|
|
| OS: | Debian GNU/Linux 2.x
Debian GNU/Linux 3.0
Debian GNU/Linux 3.1
Debian GNU/Linux unstable alias sid
|
|
| | CVE reference: | CVE-2005-2214 (Secunia mirror)
|
|
|
This advisory is currently marked as unpatched!
- Companies can be alerted when a patch is released! |
|
|
Description:
Alexander Mader has reported a security issue in Debian apt-setup, which can be exploited by malicious, local users to gain knowledge of sensitive information.
The security issue is caused due to the file "apt.conf" being created by "apt-setup" with world readable permission during installation. This makes it possible to gain knowledge of its content, which may contain sensitive information such as the proxy password.
The security issue has been reported in Debian 3.1, "apt" version 0.5.28.1. Other versions may also be affected.
Solution:
Grant only trusted users access to affected systems.
Provided and/or discovered by:
Alexander Mader
Changelog:
2006-01-31: Added CVE reference.
Original Advisory:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=305142
|
|
|
|
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
|
|
|
1356 Related Secunia Security Advisories, displaying 10
|
|
|
1. Debian update for tiff
|
|
2. Debian update for libxml2
|
|
3. Debian update for postfix
|
|
4. Debian update for pdns
|
|
5. Debian update for httracker
|
|
6. Debian update for opensc
|
|
7. Debian update for cupsys
|
|
8. Debian update for libxslt
|
|
9. Debian update for newsx
|
|
10. Debian update for ruby1.9
|
Show all related advisories
|
|
|
Send Feedback to Secunia
|
|
If you have new information regarding this Secunia advisory or a product in our database, please send it to us using either our web form or email us at vuln@secunia.com.
Ideas, suggestions, and other feedback are most welcome.
|
|
|
|
