Vulnerability Note VU#22404

telnet and rlogin URLs disclose sensitive information, including Environment variables

Once the two hosts have exchanged a WILL and a DO, the sender of the DO NEW-ENVIRON is free to request that environment variables be sent. Only the sender of the DO may send requests (IAC SB NEW-ENVIRON SEND IAC SE) and only the sender of the WILL may transmit actual environment information (via the IAC SB NEW-ENVIRON IS ... IAC SE command). Though this option may be used at any time throughout the life of the telnet connection, the exchange of environment information will usually happen at the startup of the connection. This is because many operating systems only have mechanisms for propagating environment information at process creation, so the information is needed before the user logs in.

Thus, if a telnet server requests environment variables from a telnet client that implements RFC 1572, that client will send the environment variables prior to authentication. The CERT/CC is aware of a proof-of-concept implementation of such a server.

Further, web browsers will often use help applications to deal with non-web protocols such as telnet. If a web browser is configured to use a RFC-1572-compliant telnet client as a telnet helper, then a telnet: URL can be used to obtain sensitive information from that web browser, including such environment variables as USER, HOME, PGPPASS, SSH_CLIENT and other information commonly stored in the environment. At least one Windows telnet client, UWIN, implements RFC 1572, as well as some unix telnet clients. At the present time, we have not developed an exhaustive list of clients that implement RFC 1572.

II. Impact

Systems Affected

http://andrew2.andrew.cmu.edu/rfc/rfc1572.html

Credit

Thanks to Steve Bellovin of AT&T, who reported this problem to us.

This document was written by Shawn V Hernan.

Other Information

If you have feedback, comments, or additional information about this vulnerability, please send us email.