News

Security Woes Up, as PHP and OSS Make the List

Software vulnerabilities are up this year, especially Web browser-based ones, according to a new report from IBM Internet Security Systems. The X-Force 2008 Mid-Year Trend Statistics Report, released in late July, defined the problem broadly. A vulnerability is anything that results "in a weakening or breakdown of the confidentiality, integrity, or accessibility of the computing system."

Topping the list of companies reporting the most vulnerabilities were such tech mainstays as IBM, Microsoft, Apple and Cisco Systems. Microsoft had the third most reported vulnerabilities. However, an interesting dimension to this year's report is that open source software (OSS) or free software groups, such as Mozilla's Firefox, WordPress and Joomla, also made the list of programs with security holes in them.

Larger entities such as Microsoft or IBM make the list because of the volume of software they produce, explained Tom Cross, an X-Force researcher at IBM Internet Security Systems.

"Companies that make a lot of software are subject to more disclosures," Cross added. "But we're seeing for the first time that community-developed open source such as the Drupal and Joomla content management software packages for the Web also showed up on the list."

Drupal and Joomla are both OSS packages that have both been vulnerable to recent SQL injection attacks.

Overall, the study tracked more than 3,534 disclosed vulnerabilities in software for the first half of the year, finding a five percent increase compared with the first half of 2007. Leading the list of vulnerabilities were malicious spam, phishing and different strains of malware. The nearly 80-page report found that so-called "high risk" vulnerabilities were on the rise.

A big concern of the report was the use of the PHP scripting language, which was associated with many vendor-identified vulnerabilities.

PHP is mainly used by Web developers to help create dynamic Web pages. According to the PHP Group, a research organization, PHP was installed on more than 20 million Web sites and one million Web servers as of April 2007. It is doubtless double that amount now.

The Web is emerging as the most common vector hackers are using these days for entry into networks, as well as to deliver malicious software. The report's findings confirm other research saying that attacks against trusted Web sites are up.

Moreover, hackers seem to be keeping up with security bulletins. The report concludes that 94 percent of public exploits affecting Web browser bugs were released on the same day as the public security notice.

About the Author

Jabulani Leffall is an award-winning journalist whose work has appeared in the Financial Times of London, Investor's Business Daily, The Economist and CFO Magazine, among others.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube