A remote code execution vulnerability has been reported in GoAhead versions 2.x and 3.x in the CGI handler on Linux. This impacts those sites that use dynamically linked CGI programs with GoAhead on Linux.
To help simplify and accelerate releases, we're going to focus on source code distributions only for all products.
Since the Embedthis product suite are designed for embedded use, this should impose little burden and will help focus our testing and accelerate our release pipeline.
We're releasing updates for all products with minor fixes to the underlying MPR and HTTP libraries. This means that Appweb, GoAhead and ESP get new releases.
For Appweb, we're incrementing the major release to Appweb 7. Appweb 6 becomes the Long Term Release (LTS) version and will be supported until the end of 2018. There are no breaking or major changes in Appweb 7.
But CSP is off to a slow start and is not implemented on the vast majority of web sites. Perhaps the difficulty implementing CSP is to blame?
This post examines a case study deploying CSP and has some recommendations for the social media companies to make it easier to implement CSP.
The Content Security Policy (CSP) is a powerful mechanism to prevent Cross Site Scripting (XSS) attacks which accounts for 84% of all security vulnerabilities in web sites. So you would think that such a magic bullet would be widely deployed and promoted.
Think again: CSP is implemented on less than 0.5% of web sites. Further, of those implementing sites, less than 3% are using CSP in the recommended manner that effectively mitigates Cross Site Scripting attacks. In fact, out of 21,823 sites surveyed, less than 0.02% of sites are effectively using CSP.
These are the results of a CSP survey to determine the level of CSP adoption in public web sites.