reginato / school-system-test Goto Github PK
View Code? Open in Web Editor NEWSistema de Testes
Sistema de Testes
ID: RGB_00003.005
Categoria: CWE-310: Cryptographic Issues
Reportado por: Rodrigo Reginato
Projeto: reginato/school-system-test
Criticidade:
Impacto: Alto
Probabilidade: Baixo
Criticidade: Médio
Padrões: [2010] A7 – Insecure Cryptographic Storage, CWE-311 Missing Encryption of Sensitive Data
Descrição: As aplicação armazena dados sensíveis sem a devida codificação de segurança necessária para garantir a confidencialidade de tais informações. Essas informações podem varias desde dados de cartões de crédito até senhas de acesso. No caso de comprometimento do meio de armazenamento de tais dados (através de uma outra vulnerabilidade, por exemplo) tais informações confidenciais ficariam em total exposição ao atacante.
Descrição do Impacto: Aguardando preenchimento
Solução: Utilizar mecanismos apropriados para cifrar os dados antes do armazenamento, como algoritmos de criptografia atualizados, chaves fortes, como também funções de hashing e salt.
Referência: https://www.owasp.org/index.php/Top_10_2010-A7-Insecure_Cryptographic_Storage
http://bretthard.in/2009/09/insecure-cryptographic-storage/
http://www.infosecisland.com/blogview/21796-Insecure-Cryptographic-Storage-Explained.html
http://www.troyhunt.com/2011/06/owasp-top-10-for-net-developers-part-7.html
Tipo de falha:
**Código:**teste
**Entrada de dados:**teste
**Saída de dados:**teste
Defect Tracker: https://app.conviso.com.br/scopes/193/projects/2186
ID: RGB_00003.003
Categoria: CWE-345 Insufficient Verification of Data Authenticity
Reportado por: Rodrigo Reginato
Projeto: reginato/school-system-test
Criticidade:
Impacto: Alto
Probabilidade: Alto
Criticidade: Crítico
Padrões: CWE-352 Cross-Site Request Forgery (CSRF)
Descrição: The links of forms don't are using a random token to prevent Cross-Site Request Forgery (CSRF) attacks. Without this token, an attacker could induce a real user to send forms without his authorization.
Descrição do Impacto: Aguardando preenchimento
Solução: Include a random token. The web server can use it to check if the request was really sent by the user.
Referência: https://www.owasp.org/index.php/Cross-Site_Request_Forgery_%28CSRF%29
https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)_Prevention_Cheat_Sheet
http://projects.webappsec.org/w/page/13246919/Cross%20Site%20Request%20Forgery
https://www.owasp.org/index.php/Testing_for_CSRF_%28OWASP-SM-005%29
Tipo de falha:
Código:<script>
**Entrada de dados:**input
**Saída de dados:**output
Defect Tracker: https://app.conviso.com.br/scopes/193/projects/2186
ID: REG_00002.003
Categoria: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reportado por: tconceicao
Projeto: reginato/school-system-test
Criticidade:
Impacto: Alto
Probabilidade: Alto
Criticidade: Crítico
Padrões: [2013] A3 – Cross-Site Scripting (XSS), CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Descrição: The vulnerability of Cross-Site Scripting (XSS) could allow an attacker to get sensitive information from the web application. This flaw could permit the unauthorized access of an attacker. The exploitation of a XSS flaw is made after the injection of malicious code in the scope of application, doing that, the legitimate user executes this malicious code, sending back to the attacker sensitive information like cookies.
Descrição do Impacto: Aguardando preenchimento
Solução: The first step in order to mitigate the problems of XSS is to identify all points of the application where user supplied data is used in the construction of response pages. This identification procedure should include not only the points where data from a particular request are copied directly to the response pages, but must also consider any point where the data supplied by the user is persisted by the application to be shown later, this happens, for example, with the information from the submission of a registration form.
It is recommended that validation that govern the data flow input to be made based on the context of the information being received, for example, numeric fields should receive strictly numeric characters, rejecting any different character set which the application expects. This same procedure should be followed for other form fields according to the information type they wish to accept in the application: names, e-mail, phones, among others. This goal can be achieved using regular expressions to filter out unwanted character sets considered based on the context of the information received.
With respect to the validation that follows the output stream of the application data when the information is actually used to build the answers, you should ensure that potentially malicious characters are replaced as proposed by the escape sequences defined in HTML. A well-defined set of HTML entities should be used to replace literal characters as follows:
char “ replaced by "
char ‘ replaced by '
char & replaced by &
char < replaced by <
char > replaced by >
In order to achieve excellence regarding the creation of filters, it is strongly recommended to adopt coding in HTML for any character not in the set of alphanumeric characters including whitespace (whitespace).
Referência: https://www.owasp.org/index.php/XSS
https://www.owasp.org/index.php/XSS_(Cross_Site_Scripting)Prevention_Cheat_Sheet
https://www.owasp.org/index.php/Testing_for_Cross_site_scripting
http://projects.webappsec.org/w/page/13246920/Cross%20Site%20Scripting
http://www.youtube.com/watch?v=Z9RQSnf8-g
Tipo de falha:
**Protocolo:**http
**Método:**GET
**URL:**http://localhost
Parametros:
teste
Passo a Passo:
teste
**Requisição:**teste
**Resposta:**teste
Defect Tracker: https://app.conviso.com.br/scopes/191/projects/2180
ID: REG_00002.002
Categoria: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reportado por: Rodrigo Reginato
Projeto: reginato/school-system-test
Criticidade:
Impacto: Alto
Probabilidade: Baixo
Criticidade: Médio
Padrões: [2013] A3 – Cross-Site Scripting (XSS), CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Descrição: The vulnerability of Cross-Site Scripting (XSS) could allow an attacker to get sensitive information from the web application. This flaw could permit the unauthorized access of an attacker. The exploitation of a XSS flaw is made after the injection of malicious code in the scope of application, doing that, the legitimate user executes this malicious code, sending back to the attacker sensitive information like cookies.
Descrição do Impacto: Aguardando preenchimento
Solução: The first step in order to mitigate the problems of XSS is to identify all points of the application where user supplied data is used in the construction of response pages. This identification procedure should include not only the points where data from a particular request are copied directly to the response pages, but must also consider any point where the data supplied by the user is persisted by the application to be shown later, this happens, for example, with the information from the submission of a registration form.
It is recommended that validation that govern the data flow input to be made based on the context of the information being received, for example, numeric fields should receive strictly numeric characters, rejecting any different character set which the application expects. This same procedure should be followed for other form fields according to the information type they wish to accept in the application: names, e-mail, phones, among others. This goal can be achieved using regular expressions to filter out unwanted character sets considered based on the context of the information received.
With respect to the validation that follows the output stream of the application data when the information is actually used to build the answers, you should ensure that potentially malicious characters are replaced as proposed by the escape sequences defined in HTML. A well-defined set of HTML entities should be used to replace literal characters as follows:
char “ replaced by "
char ‘ replaced by '
char & replaced by &
char < replaced by <
char > replaced by >
In order to achieve excellence regarding the creation of filters, it is strongly recommended to adopt coding in HTML for any character not in the set of alphanumeric characters including whitespace (whitespace).
Referência: https://www.owasp.org/index.php/XSS
https://www.owasp.org/index.php/XSS_(Cross_Site_Scripting)Prevention_Cheat_Sheet
https://www.owasp.org/index.php/Testing_for_Cross_site_scripting
http://projects.webappsec.org/w/page/13246920/Cross%20Site%20Scripting
http://www.youtube.com/watch?v=Z9RQSnf8-g
Tipo de falha:
**Código:**teste
**Entrada de dados:**teste
**Saída de dados:**teste
Defect Tracker: https://app.conviso.com.br/scopes/191/projects/2180
ID: RGB_00003.004
Categoria: CWE-918 Server-Side Request Forgery (SSRF)
Reportado por: Rodrigo Reginato
Projeto: reginato/school-system-test
Criticidade:
Impacto: Alto
Probabilidade: Médio
Criticidade: Alto
Padrões: n/a, CWE Incompatible
Descrição: Atacante é capaz de criar solicitações para um endereço interno ou externo. Sendo capaz de atacar redes internas que normalmente não são disponíveis para o publico em geral.
Descrição do Impacto: Aguardando preenchimento
Solução: Nunca realizar requisições a recursos externos ou internos passados pelo usuário sem uma validação. Se realmente for necessário para a aplicação fazer isso, recomenda-se criar um filtro com uma whitelist especificando os recursos que podem ser acessados, para evitar que a aplicação realize requisições a recursos internos, como exemplo o IP “127.0.0.1”, o hostname “localhost” ou IPs de rede local. Com relação aos recursos externos, pode aplicar um filtro bem similar ao anterior com o objetivo de evitar requisições maliciosas pelo servidor.
Como uma segurança adicional, é uma boa pratica a criação de regras de firewall para evitar a emissão de pacotes maliciosos gerados pela exploração desta vulnerabilidade.
Referência: http://cwe.mitre.org/data/definitions/918.html
Tipo de falha:
**Código:**teste
**Entrada de dados:**testes
**Saída de dados:**teste
Defect Tracker: https://app.conviso.com.br/scopes/193/projects/2186
ID: CVS_00220.002
Categoria: CWE-345 Insufficient Verification of Data Authenticity
Reportado por: Rodrigo Reginato
Projeto: reginato/school-system-test
Criticidade:
Impacto: Alto
Probabilidade: Médio
Criticidade: Alto
Padrões: [2010] A5 – Cross-Site Request Forgery (CSRF), CWE-352 Cross-Site Request Forgery (CSRF)
Descrição: Os ataques de CSRF permitem a uma pessoa sem autorização induzir usuários legítimos a efetuarem requisições para a aplicação sem o seu consentimento. Essas requisição podem visar a criação de usuários pré-definido na aplicação, alteração ou exclusão de dados de dados, todos sem autorização ou consentimento do usuário legítimo e vitimado.
Descrição do Impacto: Aguardando preenchimento
Solução: Recomenda-se inserir um token de sessão único nos formulários e links de todos os requests realizados pela aplicação. Este token não pode ser previsível. A utilização de CAPTCHA e o processo de re-autenticação também é recomendado em conjunto com os tokens ou quando o mesmo não puder ser utilizado. Obs.: Caso a aplicação possua alguma falha de XSS, estas medidas de prevenção podem ser burladas.
Referência: https://www.owasp.org/index.php/Cross-Site_Request_Forgery_%28CSRF%29
https://www.owasp.org/index.php/Cross-Site_Request_Forgery_(CSRF)_Prevention_Cheat_Sheet
http://projects.webappsec.org/w/page/13246919/Cross%20Site%20Request%20Forgery
https://www.owasp.org/index.php/Testing_for_CSRF_%28OWASP-SM-005%29
Tipo de falha:
**Protocolo:**asdfa
**Host:**asdfasd
Vetor:
asdfasd
Passo a Passo:
asdfasd
Defect Tracker: https://app.conviso.com.br/scopes/11/projects/2377
ID: RGB_00003.002
Categoria: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reportado por: Rodrigo Reginato
Projeto: reginato/school-system-test
Criticidade:
Impacto: Alto
Probabilidade: Alto
Criticidade: Crítico
Padrões: [2013] A3 – Cross-Site Scripting (XSS), CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Descrição: The vulnerability of Cross-Site Scripting (XSS) could allow an attacker to get sensitive information from the web application. This flaw could permit the unauthorized access of an attacker. The exploitation of a XSS flaw is made after the injection of malicious code in the scope of application, doing that, the legitimate user executes this malicious code, sending back to the attacker sensitive information like cookies.
Descrição do Impacto: Aguardando preenchimento
Solução: The first step in order to mitigate the problems of XSS is to identify all points of the application where user supplied data is used in the construction of response pages. This identification procedure should include not only the points where data from a particular request are copied directly to the response pages, but must also consider any point where the data supplied by the user is persisted by the application to be shown later, this happens, for example, with the information from the submission of a registration form.
It is recommended that validation that govern the data flow input to be made based on the context of the information being received, for example, numeric fields should receive strictly numeric characters, rejecting any different character set which the application expects. This same procedure should be followed for other form fields according to the information type they wish to accept in the application: names, e-mail, phones, among others. This goal can be achieved using regular expressions to filter out unwanted character sets considered based on the context of the information received.
With respect to the validation that follows the output stream of the application data when the information is actually used to build the answers, you should ensure that potentially malicious characters are replaced as proposed by the escape sequences defined in HTML. A well-defined set of HTML entities should be used to replace literal characters as follows:
char “ replaced by "
char ‘ replaced by '
char & replaced by &
char < replaced by <
char > replaced by >
In order to achieve excellence regarding the creation of filters, it is strongly recommended to adopt coding in HTML for any character not in the set of alphanumeric characters including whitespace (whitespace).
Referência: https://www.owasp.org/index.php/XSS
https://www.owasp.org/index.php/XSS_(Cross_Site_Scripting)Prevention_Cheat_Sheet
https://www.owasp.org/index.php/Testing_for_Cross_site_scripting
http://projects.webappsec.org/w/page/13246920/Cross%20Site%20Scripting
http://www.youtube.com/watch?v=Z9RQSnf8-g
Tipo de falha:
**Código:**teste
**Entrada de dados:**teste
**Saída de dados:**teste
Defect Tracker: https://app.conviso.com.br/scopes/193/projects/2186
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.