CPE, acronimo di Common Platform Enumeration, è uno schema standardizzato per nominare hardware, software e sistemi operativi. CPE fornisce uno schema di denominazione strutturato per identificare e classificare in modo univoco sistemi, piattaforme e pacchetti informatici in base ad attributi quali produttore, nome del prodotto, versione, aggiornamento, edizione e lingua.
CWE, acronimo di Common Weakness Enumeration, è un elenco e una categorizzazione completa delle vulnerabilità e dei difetti del software. Rappresenta un linguaggio comune per descrivere le vulnerabilità di sicurezza software nell'architettura, nella progettazione, nel codice o nell'implementazione che possono portare a vulnerabilità.
CAPEC, acronimo di Common Attack Pattern Enumeration and Classification, è una risorsa completa e pubblicamente disponibile che documenta i pattern di attacco comuni utilizzati dagli avversari negli attacchi informatici. Questa base di conoscenze mira a comprendere e articolare le vulnerabilità comuni e i metodi utilizzati dagli attaccanti per sfruttarle.
Servizi e prezzi
Aiuto e informazioni
Cerca: ID CVE, ID CWE, ID CAPEC, produttore o parole chiave nelle CVE
Per attivare i tuoi avvisi, è sufficiente essere connessi al proprio account gratuito. Se non hai ancora effettuato l'accesso, scegli una delle opzioni seguenti.
An adversary takes advantage of improper data validation to inject malicious global parameters into a Flash file embedded within an HTML document. Flash files can leverage user-submitted data to configure the Flash document and access the embedding HTML document.
Informazioni CAPEC
Flusso di esecuzione
1) Explore
[Spider] Using a browser or an automated tool, an adversary records all instances of HTML documents that have embedded Flash files. If there is an embedded Flash file, they list how to pass global parameters to the Flash file from the embedding object.
Tecnica
Use an automated tool to record all instances of URLs which have embedded Flash files and list the parameters passing to the Flash file.
Use a browser to manually explore the website to see whether the HTML document has embedded Flash files or not and list the parameters passing to the Flash file.
2) Experiment
[Determine the application susceptibility to Flash parameter injection] Determine the application susceptibility to Flash parameter injection. For each URL identified in the Explore phase, the adversary attempts to use various techniques such as DOM based, reflected, flashvars, and persistent attacks depending on the type of parameter passed to the embedded Flash file.
Tecnica
When the JavaScript 'document.location' variable is used as part of the parameter, inject '#' and the payload into the parameter in the URL.
When the name of the Flash file is exposed as a form or a URL parameter, the adversary injects '?' and the payload after the file name in the URL to override some global value.
When the arguments passed in the 'flashvars' attributes, the adversary injects '&' and payload in the URL.
If some of the attributes of the
If shared objects are used to save data that is entered by the user persistent Flash parameter injection may occur, with malicious code being injected into the Flash file and executed, every time the Flash file is loaded.
3) Exploit
[Execute Flash Parameter Injection Attack] Inject parameters into Flash file. Based on the results of the Experiment phase, the adversary crafts the underlying malicious URL containing injected Flash parameters and submits it to the web server. Once the web server receives the request, the embedding HTML document will controllable by the adversary.
Tecnica
Craft underlying malicious URL and send it to the web server to take control of the embedding HTML document.
Competenze richieste
The adversary need inject values into the global parameters to the Flash file and understand the parent HTML document DOM structure. The adversary needs to be smart enough to convince the victim to click on their crafted link.
Risorse richieste
The adversary must convince the victim to click their crafted link.
Mitigazioni
User input must be sanitized according to context before reflected back to the user. The JavaScript function 'encodeURI' is not always sufficient for sanitizing input intended for global Flash parameters. Extreme caution should be taken when saving user input in Flash cookies. In such cases the Flash file itself will need to be fixed and recompiled, changing the name of the local shared objects (Flash cookies).
Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') The product constructs a string for a command to be executed by a separate component
in another control sphere, but it does not properly delimit the
intended arguments, options, or switches within that command string.