Jan Fry

The issue allows remote authenticated users to execute arbitrary SQL commands via unspecified vectors.

Cross-site scripting (XSS) vulnerability in WebID/IISWebAgentIF.dll in RSA Authentication Agent 5.3.0.258, and other versions before 5.3.3.378, allows remote attackers to inject arbitrary web script or HTML via a URL-encoded postdata parameter. NOTE: this is different than CVE-2005-1118, but it might be the same as CVE-2008-1470.

The issue allows remote attackers to obtain access by sniffing the network, as a base64 encoded form of the `username` and `password` is placed in the ` ac` cookie for all user accounts.

The issue allows remote attackers to obtain administrative privileges by sniffing the network, as a base64 encoded form of the `username` and `password` is placed in the " ac" cookie for the admin account.

The issue concerns multiple cross-site request forgery (CSRF) vulnerabilities. These vulnerabilities allow remote attackers to perform certain actions without the victim's consent. Specifically, attackers can (1) add arbitrary accounts via the "join form" page and (2) change the privileges of arbitrary groups via the "prefs groups overview" page.

The issue allows remote attackers to gain permanent access to an account by sniffing the network, due to the use of invariant data when calculating an HMAC-SHA1 value for an authentication cookie. This makes it easier for attackers to exploit the system.

The issue concerns the handling of user authentication states. Specifically, it does not record users' authentication states and implements the logout feature solely on the client side. This makes it easier for context-dependent attackers to reuse a logged-out session.

The issue concerns multiple cross-site scripting (XSS) vulnerabilities. These vulnerabilities allow remote attackers to inject arbitrary web script or HTML via the query string to specific API endpoints, such as "my.activation.php3" and "my.logon.php3", when pre-logon sequences are enabled.

The issue allows remote attackers to inject arbitrary web script or HTML. This can be achieved through various parameters in different API endpoints, including: the `url` or `type` parameter to "docs/examples/redirect.spy"; the `x` parameter to "docs/examples/handlervalidate.spy"; the `name` parameter to "spyce/examples/request.spy"; the `Name` parameter to "spyce/examples/getpost.spy"; the `mytextarea`, `mypass`, or an empty parameter to "spyce/examples/formtag.spy"; the `newline` parameter to the default URI under "demos/chat/"; the `text1` parameter to "docs/examples/formintro.spy"; or the `mytext` or `mydate` parameter to "docs/examples/formtag.spy".

The issue allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the `url` parameter. This can be exploited by providing a malicious URL to the vulnerable application.

The issue allows remote attackers to obtain sensitive information via a direct request for "spyce/examples/automaton.spy", which reveals the path in an error message.

The issue is related to a cross-site scripting (XSS) vulnerability in the font rendering functionality. This allows remote attackers to inject arbitrary web script or HTML via the `txt` parameter to a Flash (SWF) file.

The issue allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks. This is achieved via a URL in the `nextPage` parameter in the /idm/user/login.jsp endpoint.

The issue allows remote attackers to inject frames from arbitrary web sites and conduct phishing attacks via the `helpUrl` parameter. This is related to the `/idm/help/index.jsp` endpoint.

The issue allows remote attackers to obtain sensitive information. This is achieved via a direct request to "getpath.aspx", which reveals the installation path in an error message.

A cross-site scripting (XSS) issue exists, allowing remote attackers to inject arbitrary web script or HTML via the `backurl` parameter in the download plugin.php3 file.

The issue allows remote attackers to bypass request filtering, which can lead to cross-site scripting (XSS) attacks or cause a denial of service. This can be achieved by exploiting the improper handling of comment enclosures, for example, via an xss:expression STYLE attribute in a closing XSS HTML tag.