--Re2uCLPLNzqOLVJA
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

[Sorry to reply to my own post, but...]

M. Dodge Mumford said:
> Sigint Consulting said:
> > perl -e 'print "GET \x0d/index.php\x90\x90 HTTP/1.0\n\r\n"'|nc
> > 192.168.1.3 80
> >=20
> > No alert is generated from the string above.
>=20
> [...]
>=20
> > We are not sure how much this may buy an attacker as the CR character
> > may mess up any requests to the webserver, further research is needed
> > on this.
>=20
> I performed this research while developing NFR's web signatures, and found
> that all web servers I tested (several years ago) handled end-of-lines us=
ing
> "\x0d\x0a" and "\x0a" interchangeably. If you find a web server that
> interprets "index.php" in the example above as an actual filename, I for =
one
> would be very interested in knowing about it.

Apparently my memory is failing. If I performed this test, I remembered the
results incorrectly. Mea culpa.


--=20

Dodge

--Re2uCLPLNzqOLVJA
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)

iD8DBQFEgbUJ4Cw5+cTF6YkRAuCoAKCUlJvUTRmaFLPY1DPAWk zVyqFlKwCfYgYI
aWq5+SDOCR7ITFS5dP+MERc=
=y85g
-----END PGP SIGNATURE-----

--Re2uCLPLNzqOLVJA--