| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 21 Dec 2012 01:45:10 +0100 From: Vulnerability Lab <research@...nerability-lab.com> To: full-disclosure@...ts.grok.org.uk Subject: Re: Paypal Core Bug Bounty #3 - Persistent Web Vulnerability "Exactly how is the session hijacking/phishing/web content manipulation _persistent_? Just because the payload is _stored_ does not necessarily mean that is it always running. & [...]" The stored context can be used by another user to find the person with the details to execute. The first module when adding parses the context but does not change the tags or scripts. The execution happens in a third module which is also located in the core functions. Low user interaction is required because you need to get in contact with the person by a accepted transaction (after it your are saved to the contacts) or click a mail link. Only the accept or click is a low user interaction because nothing else was required. "How is THAT a... I am miss" Paypal allows to merge accounts and use it with multiple persons or companies. The addressbook is also synced and visible for all parties which are bound to the account. The attack can be executed local in multiple accounts or after an transaction or add when processing to search the contact. -- VULNERABILITY RESEARCH LABORATORY LABORATORY RESEARCH TEAM CONTACT: research@...nerability-lab.com _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
Powered by blists - more mailing lists