tomvangoethem

8 ms·

31.
Developer runs program that automatically tweets anything he copies(twitter.com)
2 points by tomvangoethem 13y ago|0 comments
32.
Prezi Got Pwned: A Tale of Responsible Disclosure(engineering.prezi.com)
14 points by tomvangoethem 13y ago|0 comments
33.
by tomvangoethem 13y ago
Except for causing annoyances, the truncation of data may also have security implications. Last year, I found that WordPress (which has the utf8 character set by default), was vulnerable to PHP object injection because their filter could be
34.
Why I removed my sensitive files from Google Drive(vagosec.org)
11 points by tomvangoethem 13y ago|2 comments
35.
Remote Code Execution exploit in WordPress 3.5.1(vagosec.org)
3 points by tomvangoethem 13y ago|0 comments
36.
by tomvangoethem 13y ago
Make that `<link rel=stylesheet href= http://ø.xx>` as JavaScript won't execute in recent mail clients.
37.
by tomvangoethem 13y ago
How would you describe a well-behaved e-mail client with regards to this vulnerability? The phishing attack I described in my blog post affects all e-mail clients that are able to render HTML and CSS. As for rendering remotely included CSS,
38.
by tomvangoethem 13y ago
Seems there is some misconception here: 1. I was not complaining that I did not get paid for this bug, but that different Bug Bounty programs have different thresholds on whether a vulnerability qualifies for a monetary reward. This seems l
39.
by tomvangoethem 13y ago
I don't think that giving me some money would have refrained me from writing this blog post. The main issue here is that it was not recognized as security sensitive, and would most likely not be fixed if I didn't insist on it.
40.
WordPress before 3.6.1: PHP Object Injection(vagosec.org)
5 points by tomvangoethem 13y ago|2 comments
41.
by tomvangoethem 13y ago
I agree on the subject line (which is "Verify your email address") and that the mail is sent from "Google Scholar Citations", but as it was possible to include arbitrary CSS files, the content could be changed to pretty
42.
by tomvangoethem 13y ago
A PoC was produced (see the part of the guy named `</a><a id=a href= http://goo.gl/CQtK5F><link rel=stylesheet href=" http://tomvglabs.be/css.php">` ), and was sent to the Goog
43.
by tomvangoethem 13y ago
Not quite, if you were the attacker, you'd update your own name to `Mr Test<!--BAD STUFF HERE` and then try to change your e-mail to victim@some.edu and perform the phishing attack on the victim or yes, as pudquick put it more nicel
44.
by tomvangoethem 13y ago
I was expecting them to put my name up there by the time I posted the blog, should be there in the near future though...
45.
Why you should not trust emails sent from Google(vagosec.org)
353 points by tomvangoethem 13y ago|94 comments