Full Disclosure mailing list archives
RE: How T-Mobil's network was compromised
From: "Allan" <fulldisclosure () wateraxe demon nl>
Date: Sun, 20 Feb 2005 21:40:07 +0100
[quote] 3) (and based on a recent example, I just can't find the reference... it was some PHP app): Input URLs are examined for "../" and converted into "./". The function worked correctly, no flaw from a programming perspective. However, input of ".../" was converted to "../" as planned, but leaving the application still vulnerable. (Note: I don't think the fix to that problem was all that great. What should have occurred is a check for "../" in a loop. Change and replace as often as "../" is found. There was no such loop in the suggested fix afair) [/quote] I think this was the recent mailman vulnerability... _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
Current thread:
- Re: How T-Mobil's network was compromised, (continued)
- Re: How T-Mobil's network was compromised Ill will (Feb 17)
- Re: How T-Mobil's network was compromised bkfsec (Feb 19)
- Re: How T-Mobil's network was compromised Valdis . Kletnieks (Feb 19)
- Re: How T-Mobil's network was compromised Willem Koenings (Feb 19)
- Re: How T-Mobil's network was compromised Frank Knobbe (Feb 19)
- Re: How T-Mobil's network was compromised Willem Koenings (Feb 19)
- Re: How T-Mobil's network was compromised Valdis . Kletnieks (Feb 19)
- Re: How T-Mobil's network was compromised Frank Knobbe (Feb 20)
- Re: How T-Mobil's network was compromised Willem Koenings (Feb 20)
- Re: How T-Mobil's network was compromised Frank Knobbe (Feb 20)
- RE: How T-Mobil's network was compromised Allan (Feb 20)
- Re: How T-Mobil's network was compromised Ill will (Feb 17)