Skip to content
Fencer Vulns
high 7.5

CVE-2005-3757 in the critical feed json

The Saxon XSLT parser in Google Mini Search Appliance, and possibly Google Search Appliance, allows remote attackers to obtain sensitive in…

published 2005-11-22 20 y ago modified 2026-06-16 4 mo ago also EUVD-2005-3752

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
41.3%
EPSS 41.3% chance of exploitation in 30 days, percentile 98%
public exploits
3
Metasploit, Exploit-DB

Summary

The Saxon XSLT parser in Google Mini Search Appliance, and possibly Google Search Appliance, allows remote attackers to obtain sensitive information and execute arbitrary code via dangerous Java class methods in select attribute of xsl:value-of tags in XSLT style sheets, such as (1) system-property, (2) sys:getProperty, and (3) run:exec.

Patch / fix

Timeline

  1. First public exploit (Metasploit exploit/unix/webapp/google_proxystylesheet_exec)
  2. Published

Exploit prediction

41.25% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Metasploit exploit/unix/webapp/google_proxystylesheet_exec Google Appliance ProxyStyleSheet Command Execution metasploit exploit, excellent rank, 2005-08-16
  • EDB-16907 Google Appliance ProxyStyleSheet - Command Execution (Metasploit) webapps, 2010-07-01
  • EDB-1333 Google Search Appliance - proxystylesheet XSLT Java Code Execution (Metasploit) remote, 2005-11-20
  • metasploit.com http://metasploit.com/research/vulns/google_proxystylesheet/ referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/15509 referenced PoC, tagged "exploit" by a source, unverified
  • securitytracker.com http://securitytracker.com/id?1015246 referenced PoC, tagged "exploit" by a source, unverified
  • osvdb.org http://www.osvdb.org/20981 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.