(PVS) Signatures - Tenable Network Security

Google Chrome < 5.0.375.127 Multiple Vulnerabilities
PVS ID: 5644 FAMILY: Web Clients RISK: HIGH NESSUS ID:48383
Description: Synopsis :\n\nThe remote host contains a web browser that is vulnerable to multiple attack
vectors.\n\nFor your information, the observed version of Google Chrome installed on the
remote host is %L.\n\nVersions of Google Chrome earlier than 5.0.375.127 are potentially
affected by multiple vulnerabilities :\n\nA memory corruption issue with file dialog. (Bug
45400)\n\nA memory corruption issue with SVGs. (Bug 49596)\n\nAn issue relating to a
bad cast with text editing. (Bug 49268)\n\n - A possible address bar spoofing vulnerability
caused by a history bug. (Bug 49964)\n\n - A memory corruption issue in MIME type
handling. (Bugs 50515, 51835)\n\nA crash on shutdown due to a notifications bug. (Bug
50553)\n\nOmnibox autosuggest is enabled when a user might be typing a password. (Bug
51146)\n\nA memory corruption issue in Ruby support. (Bug 51654)\n\nA memory
corruption issue in Geolocation support. (51670)
Solution: Upgrade to Google Chrome 5.0.375.127 or later.
CVE-2010-3120
Database TDS Failed Login Detection
PVS ID: 5645 FAMILY: Database RISK: INFO NESSUS ID:Not Available
Description: The following UserID just failed a SQL login
Solution: N/A
realtimeonly
CVE Not available
MySQL Community Server 5.1 < 5.1.49 Multiple Denial of Service Vulnerabilities
PVS ID: 5646 FAMILY: Database
Passive Vulnerability Scanner (PVS) Signatures
RISK:
MEDIUM
NESSUS ID:48759
Description: Synopsis :\n\nThe remote database server is vulnerable to multiple denial of service
attacks.\n\nFor your information, the observed version of MySQL Community Server is
%L.\n\nVersions of MySQL Community Server 5.1 earlier than 5.1.49 are potentially
affected by multiple vulnerabilities :\n\n - After changing the values of the
'innodb_file_format' or 'innodb_file_per_table' configuration parameters, DDL statements
could cause a server crash. (Bug #55039)\n\nJoins involving a table with a unique SET
column could cause a server crash. (Bug #54575)\n\nIncorrect handling of NULL
arguments could lead to a crash for IN() or CASE operations when ULL arguments were
either passed explicitly as arguments (for IN()) or implicitly generated by the WITH
ROLLUP modifier which could lead to a crash. (Bug #54477)\n\n - A malformed argument
to the BINLOG statement could result in Valgrind warnings or a server crash. (Bug
#54393)\n\n - Use of TEMPORARY InnoDB tables with nullabale columns could cause a
server crash. (Bug #54044)\n\n - The server could crash if there were alternate reads from
two indexes on a table using the HANDLER interface. (Bug #54007)\n\n - Using
Family Internet Services 1519