|
pPIM Multiple Vulnerabilities
|
|
Secunia Advisory:
|
SA31424
|
|
|
Release Date:
|
2008-08-12
|
|
Last Update:
|
2009-02-25
|
|
Popularity:
|
1,471 views
|
|
|
Critical:
|
Highly critical
|
|
Impact:
|
Security Bypass
Cross Site Scripting
Manipulation of data
Exposure of sensitive information
System access
|
|
Where:
|
From remote
|
|
Solution Status:
|
Unpatched
|
|
| Software: | pPIM 1.x
|
|
|
Secunia CVSS-2 Score:
|
Available in Secunia business solutions 
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities
|
|
| Advisory Content (Page 1 of 3) | [ 1 ] [ 2 ] [ 3 ] | |
|
Description:
Some vulnerabilities have been discovered in pPIM (Phlatline's Personal Information Manager), which can be exploited by malicious people or users to disclose potentially sensitive information, manipulate data, and compromise a vulnerable system, and by malicious people to conduct cross-site scripting and script insertion attacks and bypass certain security restrictions.
1) Input passed to the "file" parameter in upload.php (when "mode" is set to "delfile") is not properly sanitised before being used. This can be exploited to delete arbitrary files via directory traversal attacks.
Successful exploitation may require valid user credentials (but see #3).
2) Input passed to the "date" parameter in events.php is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.
Successful exploitation may require that the target user has valid user credentials.
3) A vulnerability is caused due to improper access restriction in changepassword.php. This can be exploited to change the password without valid user credentials.
4) A vulnerability is caused due to missing restrictions on what file types that users are allowed to upload in upload.php. This can be exploited to execute arbitrary PHP code.
Successful exploitation may require valid user credentials (but see #3).
5) Input passed to the "id" parameter in notes.php is not properly verified before being used to load files. This can be exploited to e.g. disclose potentially sensitive information via directory traversal attacks.
Successful exploitation may require valid user credentials (but see #3).
6) The "password.dat" file is stored with insecure permissions inside the web root. This can be exploited to gain knowledge of sensitive information (e.g. password hashes) by requesting the file directly.
7) The "templates/header.html" file does not properly restrict access to the application when password protection is enabled. This can be exploited to access password protected parts of the application by appending "?login=1" to the desired script's URL (e.g. http://host/ppim/contact.php?login=1").
8) The application does not properly restrict access to the "notes.php" script when password protection is enabled. This can be exploited to create and delete notes by posting to the mentioned script directly.
9) Input posted to the "notes.php" script is not properly sanitised before being used. This can be exploited to insert arbitrary HTML and script code, which will be executed in a user's browser session in context of an affected site if the malicious note is displayed.
10) "email/[username].email" files are stored with insecure permissions inside the web root. This can be exploited to gain knowledge of sensitive information (e.g. mail server address, user name, and password) by requesting the files directly.
11) The application does not properly restrict access to the "sendmail.php" script when password protection is enabled. This can be exploited to send e-mails by posting to the mentioned script directly.
12) Input passed to the "makegroup.php" script is not properly sanitised before being written to a link file, which can be exploited to inject and execute arbitrary PHP code.
The vulnerabilities are confirmed in version 1.01 and reported in version 1.0. Other versions may also be affected.
Change Page:
[ 1 ] [ 2 ] [ 3 ]
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
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.
|
