My company has a web application hosted at an application server provider
site. We are using James 2.3.1 to provide email functionality to our app.
James runs as a service on a Windows 2003 server.
We contracted to have a penetration test done against our application to
determine potential vulnerabilities with our application and with our
hosting facility. The test pointed out two issues with our James
installation:
#1
SmtpRelayUucp : SMTP servers may perform third-party relaying on UUCP
style addresses
Some SMTP (Simple Mail Transfer Protocol) servers will allow third-party
remailing ("relaying") when the
attacker uses UUCP (Unix to Unix Copy) style addresses. UUCP addresses are
those that use the '%'
character as a delimiter, as in [EMAIL PROTECTED] This could
allow an attacker to bounce email
through your servers and obfuscate its true origin.
#2
SMTPforgery : SMTP server allows fake hostnames in HELO
The SMTP server was found to accept any hostname issued to it in the HELO
command. This lack of
authorization could allow users to more easily forge mail from your mail
server.
Are either of these two issues something to worry about and does anyone
have any configuration changes in James that would close these
vulnerabilities?
Thanks.
John Rose
Email: [EMAIL PROTECTED]
********************************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee; access to this
email by anyone else is unauthorized.
If you are not the intended recipient: (1) you are kindly requested
to return a copy of this message to the sender indicating that you
have received it in error, and to destroy the received copy; and (2)
any disclosure or distribution of this message, as well as any action
taken or omitted to be taken in reliance on its content, is prohibited
and may be unlawful.
********************************************************************************
