Pine Unix Username Account Information Leakage Vulnerability

BID:4963

Info

Pine Unix Username Account Information Leakage Vulnerability

Bugtraq ID: 4963
Class: Design Error
CVE:
Remote: Yes
Local: No
Published: Jun 08 2002 12:00AM
Updated: Jun 08 2002 12:00AM
Credit: Vulnerability discovery credited to Roger Marquis <[email protected]>.
Vulnerable: University of Washington Pine 4.44
+ EnGarde Secure Linux 1.0.1
+ Redhat Enterprise Linux AS 2.1 IA64
+ Redhat Enterprise Linux AS 2.1
+ Redhat Enterprise Linux ES 2.1 IA64
+ Redhat Enterprise Linux ES 2.1
+ Redhat Enterprise Linux WS 2.1 IA64
+ Redhat Enterprise Linux WS 2.1
+ Redhat Linux Advanced Work Station 2.1
+ Sun Cobalt Qube 3
+ Sun Cobalt RaQ 4
+ Sun Cobalt RaQ 550
+ Sun Cobalt RaQ XTR
+ Sun Linux 5.0.7
+ Sun Linux 5.0
+ SuSE Linux 8.1
+ SuSE Linux 8.0 i386
+ SuSE Linux 8.0
University of Washington Pine 4.33
- FreeBSD FreeBSD 4.4
- FreeBSD FreeBSD 4.3
- FreeBSD FreeBSD 4.2
+ HP Secure OS software for Linux 1.0
+ Redhat Linux 7.2 ia64
+ Redhat Linux 7.2 i386
+ Redhat Linux 7.1 ia64
+ Redhat Linux 7.1 i386
+ Redhat Linux 7.1 alpha
+ SuSE Linux 7.3 sparc
+ SuSE Linux 7.3 ppc
+ SuSE Linux 7.3 i386
+ SuSE Linux 7.3
+ SuSE Linux 7.2 i386
+ SuSE Linux 7.2
+ SuSE Linux 7.1 sparc
+ SuSE Linux 7.1 ppc
+ SuSE Linux 7.1 alpha
+ SuSE Linux 7.1
University of Washington Pine 4.30
University of Washington Pine 4.21
+ Redhat Linux 7.0 i386
+ Redhat Linux 7.0 alpha
+ Redhat Linux 6.2 sparc
+ Redhat Linux 6.2 i386
+ Redhat Linux 6.2 alpha
+ Slackware Linux 7.1
+ Slackware Linux 7.0
Not Vulnerable:

Solution / Fix

Pine Unix Username Account Information Leakage Vulnerability

Solution:
An untested patch has been made available by Roger Marquis <[email protected]>:

--------------------------------------------------------------------
--- pine/send.c.orig Tue Jan 8 12:59:37 2002
+++ pine/send.c Sat Mar 9 09:17:08 2002
@@ -3989,12 +3989,15 @@

outgoing->return_path = rfc822_cpy_adr(outgoing->from);

+
/*
* Don't ever believe the sender that is there.
* If From doesn't look quite right, generate our own sender.
*/
+ /**** fix u-washington anti-privacy loophole
if(outgoing->sender)
mail_free_address(&outgoing->sender);
+ /****

/*
* If the LHS of the address doesn't match, or the RHS
@@ -4003,6 +4006,7 @@
*
* Don't add a personal_name since the user can change that.
*/
+ /**** fix u-washington anti-privacy loophole
if(!outgoing->from
|| !outgoing->from->mailbox
|| strucmp(outgoing->from->mailbox, ps_global->VAR_USER_ID) != 0
@@ -4014,6 +4018,7 @@
outgoing->sender->mailbox = cpystr(ps_global->VAR_USER_ID);
outgoing->sender->host = cpystr(ps_global->hostname);
}
+ /****

/*----- Message is edited, now decide what to do with it ----*/
if(editor_result & (COMP_SUSPEND | COMP_GOTHUP | COMP_CANCEL)){
--------------------------------------------------------------------

© CVE.report 2026

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. It is the responsibility of user to evaluate the accuracy, completeness or usefulness of any information, opinion, advice or other content. EACH USER WILL BE SOLELY RESPONSIBLE FOR ANY consequences of his or her direct or indirect use of this web site. ALL WARRANTIES OF ANY KIND ARE EXPRESSLY DISCLAIMED. This site will NOT BE LIABLE FOR ANY DIRECT, INDIRECT or any other kind of loss.

CVE, CWE, and OVAL are registred trademarks of The MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. This site includes MITRE data granted under the following license.

Free CVE JSON API cve.report/api

CVE.report and Source URL Uptime Status status.cve.report