Page 7 of 73 results (0.008 seconds)

CVSS: 7.5EPSS: 0%CPEs: 50EXPL: 0

27 Jun 2006 — Unspecified vulnerability in IBM WebSphere Application Server (WAS) before 6.0.2.11, when fileServingEnabled is true, allows remote attackers to obtain JSP source code and other sensitive information via "URIs with special characters." Una vulnerabilidad no especificada en IBM WebSphere Application Server (WAS) antes de v6.0.2.11, cuando fileServingEnabled esta puesto a TRUE, permite a atacantes remotos obtener el código fuente JSP y otra información sensible a través de una "URI con caracteres especiales." • http://secunia.com/advisories/20732 •

CVSS: 10.0EPSS: 0%CPEs: 50EXPL: 0

27 Jun 2006 — Unspecified vulnerability in IBM WebSphere Application Server before 6.0.2.11 has unknown impact and attack vectors because the "UserNameToken cache was improperly used." Vulnerabilidad sin especificar en el servidor de aplicaciones IBM WebSphere en versiones anteriores a la v6.0.2.11 tiene un impacto y vectores de ataque desconocidos debido a que "la caché UserNameToken no es usada apropiadamente". • http://secunia.com/advisories/20732 •

CVSS: 10.0EPSS: 1%CPEs: 13EXPL: 0

17 May 2006 — IBM WebSphere Application Server 5.0.2 and earlier, 5.1.1 and earlier, and 6.0.2 up to 6.0.2.7 records user credentials in plaintext in addNode.log, which allows attackers to gain privileges. • http://archives.neohapsis.com/archives/bugtraq/2006-05/0175.html •

CVSS: 6.1EPSS: 1%CPEs: 20EXPL: 1

17 May 2006 — Cross-site scripting (XSS) vulnerability in the 500 Internal Server Error page on the SOAP port (8880/tcp) in IBM WebSphere Application Server 5.0.2 and earlier, 5.1.x before 5.1.1.12, and 6.0.2 up to 6.0.2.7, allows remote attackers to inject arbitrary web script or HTML via the URI, which is contained in a FAULTACTOR element on this page. NOTE: some sources have reported the element as "faultfactor," but this is likely erroneous. • https://www.exploit-db.com/exploits/28981 • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •

CVSS: 7.5EPSS: 1%CPEs: 5EXPL: 0

17 May 2006 — IBM WebSphere Application Server 5.0.2 (or any earlier cumulative fix) and 5.1.1 (or any earlier cumulative fix) allows EJB access on Solaris systems via a crafted LTPA token. • http://archives.neohapsis.com/archives/bugtraq/2006-05/0175.html •

CVSS: 9.8EPSS: 0%CPEs: 5EXPL: 0

17 May 2006 — Unspecified vulnerability in IBM WebSphere Application Server 5.0.2 and earlier, and 5.1.1 and earlier, has unknown impact and attack vectors related to "Inserting certain script tags in urls [that] may allow unintended execution of scripts." • http://archives.neohapsis.com/archives/bugtraq/2006-05/0175.html •

CVSS: 9.8EPSS: 0%CPEs: 3EXPL: 0

17 May 2006 — WebSphere Application Server 5.0.2 (or any earlier cumulative fix) stores admin and LDAP passwords in plaintext in the FFDC logs when a login to WebSphere fails, which allows attackers to gain privileges. • http://archives.neohapsis.com/archives/bugtraq/2006-05/0175.html •

CVSS: 7.8EPSS: 0%CPEs: 1EXPL: 0

22 Nov 2005 — Double free vulnerability in the BBOORB module in IBM WebSphere Application Server for z/OS 5.0 allows attackers to cause a denial of service (ABEND). • http://secunia.com/advisories/17658 • CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer •

CVSS: 7.5EPSS: 33%CPEs: 3EXPL: 0

04 Nov 2005 — IBM WebSphere Application Server 5.0.x before 5.02.15, 5.1.x before 5.1.1.8, and 6.x before fixpack V6.0.2.5, when session trace is enabled, records a full URL including the queryString in the trace logs when an application encodes a URL, which could allow attackers to obtain sensitive information. • http://securitytracker.com/id?1015134 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •

CVSS: 7.2EPSS: 1%CPEs: 2EXPL: 1

30 Jun 2005 — IBM WebSphere 5.1 and WebSphere 5.0 allows remote attackers to poison the web cache, bypass web application firewall protection, and conduct XSS attacks via an HTTP request with both a "Transfer-Encoding: chunked" header and a Content-Length header, which causes WebSphere to incorrectly handle and forward the body of the request in a way that causes the receiving server to process it as a separate HTTP request, aka "HTTP Request Smuggling." • http://seclists.org/lists/bugtraq/2005/Jun/0025.html •