PHP exploit code plants itself in GIF
599984
Blog: Security researchers found PHP exploit code embedded in a GIF on a major image hosting site, slipping through the proverbial gates with the aid of a legitimate image at the beginning of the file, according to security researchers.
44372
A flaw in the way the Firefox and Opera browsers handle an image file could allow an attacker to see what Web sites a person has visited.
543022
Code that exploits a serious, yet-to-be-patched hole in Microsoft's Web browser has been posted on the Net.
347238
Hole allows attackers to create fake Web sites that look genuine.
105905
Blog: Original researcher makes public his own exploit code.
541647
On Codewalkers.com today, there's a new tutorial posted concerning some of the looping features PHP has to offer.
663988
According to this new post on the PHP Security Blog, there's a new META tag the Suhosin extension includes in the output of a phpinfo page to help resolve some of the issues with Google (and buddies) storing the contents of the page, giving a potential attacker information they could exploit.   [The] extra META TAG to the HTML output of phpinfo() that forbids indexing and archiving by robots. For fairness reasons following the embedded links is still allowed to robots, because a lot of projects [...] to get at least a few backlinks for their work, that might result in a better search engine positioning.   The patch can be downloaded from their site.
345464
php|architect has a new note about a few PHP vulnerabilities:
357182
In a new post to his blog, Chris Hartjes, spurred on by an article in the latest edition of php|architect magazine (covering protecting your code), has shared a few opinions starting with a certain paragraph near the end.   To start, I will focus on the paragraph above. What I get out of that is that if only your source was closed and hidden from prying eyes, it would not have bugs in it. Which is, of course, total nonsense. Code has bugs because it's open and they feel safer? There are two kinds of bugs: application bugs (which is the code I would write) and system bugs (in this case, bugs that that appear from PHP itself). I'm sorry, but there is nothing I can do if there is a bug in PHP that causes my application to crash except to point this bug out to the people who have the ability to fix it.   He goes on to talk more about how protection like this (the article talks about using the IonCube Encoder) will not stop someone if they're really determine to get at the code underneath the encryption. His only suggestion is to make an application good enough that people wouldn't want to try to steal it as much and would rather pay for their version.   Encode your stuff if you want, but be aware that the minute you choose to do that you are telling your customers "I don't trust you" and I have a hard time understanding a business model that assumes people are going to want to steal the stuff you sell.
9540
The Hardened-PHP Project has released a new vulnerability for the PHProjekt groupware software.    While searching for applications that are vulnerable to a new class of vulnerabilities inside PHP applications we took a quick look into the current PHProjekt source code and discovered that a (remote) include vulnerability had been (re)introduced.   By overwriting a variable with user input it is possible to inject and execute arbitrary PHP code. Overwriting this variable is possible regardless of the register_globals setting.    They give a few more details further down the posting and note that users should download and install the latest version (at the time of this post, 5.1.2).
52789
The flaw exploited by the most recent versions of the worm such as Santy.C or Santy.E is more general than the original, and can occur anywhere a site designer has left the door open for the inclusion of arbitrary files into PHP scripts, reports IDG News
178847
A bug in Microsoft&#39;s Internet Security and Acceleration (ISA) Server 2000 and Proxy Server 2.0 can let hackers spoof Web content, such as a trusted site, with their own fake content, the Redmond
90003
As the International PHP Maagzine reports today there's been a file inclusion vulnerability found (from Secunia) in the DreamStats package:   Secunia's latest advisory points out a vulnerability in DreamStats, which could be exploited by remote attackers to execute arbitrary commands. This issue is due to an input validation error in the "index.php" script that does not validate the "rootpath" parameter, which could be exploited by remote attackers to include malicious PHP scripts and execute arbitrary commands with the privileges of the web server.   Those at risk are systems running versions 4.2 and prior and should update immediately. DreamStats is a package for displaying the statistics for Call of Duty related games on a website.
312317
If you took the photo of a Chihuahua at www.flickr.com/photos/benvoluto/216323527/, you have caused a Web sensation.
247778
From the PHP-Coding-Practices.com site today, there's a new article that discusses some of the top security vulnerabilities that surround PHP applications.   PHP has allowed people with all sorts of backgrounds to put their ideas on the web. With several hundred million web pages programmed in PHP, security plays a big deal for us web programmers. In this introduction I will outline the most common security vulnerabilities in PHP scripts.   Topics include:  All Input is Tainted Cross-Site Scripting SQL Injection Code Injection Command Injection Session and Cookie Security Securing File Access   Each has their own explanation (including code where needed) that talks about what the issue is and a hint at its solution. This post will be followed by more tutorials that will focus on each of the topics in more detail with solutions to help solve and prevent them from happening in your application.
97618
Code that claims to partially exploit a weakness in Microsoft software&#39;s handling of image files has been published on the Internet.
16648
Opt-out button in spam used to run exploit