DOCSLIB.ORG

Application Security Testing Tools Study and Proposal

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Application Security Testing Tools Study and Proposal Application Security Testing Tools Study and Proposal Miro Casanova Páez Máster Universitario en Seguridad de las Tecnologías de la Información y de las Comunicaciones. (MISTIC) Seguridad Empresarial Pau del Canto Rodrigo Victor Garcia Font 12/2020 i Esta obra está sujeta a una licencia de Reconocimiento-NoComercial- SinObraDerivada 3.0 España de Creative Commons ii FICHA DEL TRABAJO FINAL Título del trabajo: Application Security Testing Tools Study and Proposal Nombre del autor: Miro Casanova Páez Nombre del consultor/a: Pau del Canto Rodrigo Nombre del PRA: Victor Garcia Font Fecha de entrega: 12/2020 Titulación: Máster Universitario en Seguridad de las Tecnologías de la Información y de las Comunicaciones (MISTIC) Área del Trabajo Final: Seguridad Empresarial Idioma del trabajo: Inglés Palabras clave SAST, DAST Resumen del Trabajo Hoy en día es una evidencia la necesidad de un menor tiempo de lanzamiento al mercado de las aplicaciones. Sin embargo, aunque el tiempo necesario para desarrollarlas se reduzca, todavía se necesita poder ofrecer aplicaciones con- fiables y seguras. Esto era ya es una tarea difícil, y ahora lo es aún más con las restricciones de tiempo y la rápida evolución de las tecnologías. Los erro- res ocultos en el software pueden traducirse en vulnerabilidades de seguridad que potencialmente permitan a los atacantes poner en peligro los sistemas y aplicaciones. Hay hackers y crackers que pueden estar al acecho para obtener nuestra valiosa información personal. Por lo tanto, estas aplicaciones deben ser seguras y con- fiables ya que nuestra información o documentos privados se almacenan en es- tas aplicaciones de n capas. Cada año miles de estas vulnerabilidades se des- velan públicamente en el Common Vulnerabilities and Exposures database [23]. Estas vulnerabilidades son a menudo ocasionadas por errores sutiles cometidos por programadores y pueden propagarse rápidamente debido a la prevalencia del software de código abierto así como a la reutilización de código. Nos enfrentamos al dilema de la necesidad de acelerar el proceso de desarro- llo de software y al mismo tiempo el requisito de ofrecer aplicaciones fiables y seguras. Hay muchos enfoques para abordar este problema que van desde adaptar el proceso de desarrollo de software a soluciones técnicas más concre- tas. En este TFM intentaremos analizar el uso de una o varias herramientas automatizadas para verificar si las aplicaciones en construcción tienen el nivel de seguridad requerido mediante la detección de posibles vulnerabilidades o errores que podría causar un funcionamiento no deseado. Este enfoque aborda la detección de código vulnerable durante el curso del ciclo de desarrollo de software. Abstract: iii Nowadays the need for a shorter time-to-market of applications is evident. How- ever, even though the time needed for developing them gets reduced, we still need to be able to deliver reliable and secure apps. This was already a challen- ging task, and it is even more so with the time restrictions and the rapidly evolving technologies. Hidden flaws in software can result in security vulnerabilities that potentially allow attackers to compromise systems and applications. There are hackers and crackers who may be keeping an eye on our valuable personal information. Hence, these applications need to be secured and should be reliable since our private and important information or documents are stored on the back end of these n-tiered applications. Each year thousands of such vulnerabilities are reported publicly to the Common Vulnerabilities and Exposures database [23]. These vulnerabilities are often caused by subtle errors made by programmers and can propagate quickly due to the prevalence of open-source software and code reuse. We are confronted with the dilemma of the need for speeding up the software de- velopment process while at the same time the requirement of delivering reliable and secure applications. There are many approaches for tackling this problem which range from adapting the software development process to more concrete technical solutions. In this TFM we will try to analyse the use of one or several automatized software tools for verifying whether the application under construc- tion has the required level of security by detecting potential vulnerabilities or flaws that could cause an undesired misfunction. This approach addresses the detec- tion of vulnerable code during the course of the software development cycle. iv Contents List of Figures vi 1 Introduction1 1.1 Context and motivation . .1 1.2 Objectives . .1 1.3 Methodology . .3 1.4 Planning . .3 1.5 Summary of the obtained product . .4 1.6 Description next chapters of this work . .4 2 State of the art5 2.1 SAST, DAST, IAST, SCA Overview . .6 2.2 SAST . .7 2.2.1 SAST tools on the market . .8 SonarQube . .9 Coverity . .9 SpotBugs . .9 AppScan Source . 10 CheckMarx . 10 2.3 DAST . 11 2.3.1 DAST tools on the market . 12 AppScan Standard . 12 Managed DAST Synopsys . 12 OWASP Zed Attack Proxy (ZAP) . 13 Arachni . 14 Subgraph Vega . 15 2.4 IAST . 17 2.4.1 IAST tools on the market . 17 Contrast Assess . 17 Synopsys Seeker . 18 2.5 SCA . 18 2.5.1 SCA tools on the market . 19 OWASP dependency check . 20 OWASP Dependency Track . 21 Synopsys Black Duck . 22 Snyk............................. 22 2.6 Table: Summary of tools . 23 v 3 Benchmarks 24 3.1 OWASP Benchmark . 24 3.2 WAVSEP . 27 3.3 SAMATE . 30 3.4 Other benchmarks . 31 4 Software Security Assurance Tools Selection 36 4.1 Selection criteria . 36 4.2 Organisation’s ecosystem . 39 4.3 Selection and exclusion of tools . 40 4.3.1 SAST selection . 40 4.3.2 DAST selection . 41 4.3.3 IAST selection . 42 4.3.4 SCA selection . 42 4.4 Summary of selection . 43 4.5 Implementation of Quick Wins . 43 4.5.1 SonarQube . 43 4.5.2 SpotBugs . 45 4.5.3 Find Security Bugs . 46 5 Conclusions 47 Bibliography 53 vi List of Figures 2.1 Spotbugs Maven GUI - Scan OWASP Benchmark project . 10 2.2 OWASP ZAP Desktop Interface - Quick scan . 13 2.3 OWASP ZAP Quick scan Alert . 14 2.4 Arachni scanning www.uoc.edu . 15 2.5 Vega scanning overview . 16 2.6 Vega scanning - detail on high risk XSS vulnerability . 16 2.7 OWASP dependency check on OWASP Benchmark project . 20 2.8 OWASP dependency check details . 21 3.1 Diagram OWASP Benchmark true and false positives . 25 3.2 OWASP Benchmark results . 26 3.3 Results of the Julia tool with OWASP Benchmark . 27 3.4 Excerpt of WAVSEP results . 28 3.5 TP, FP, TN results in Idrissi et al. 29 3.6 Overview of the metrics results in Idrissi et al. 30 3.7 Parfait tool results . 31 3.8 Benchmark results of Bermejo et al. for TP and FP . 32 3.9 Metrics obtained for the different tools . 33 3.10 Lab environment used for penetration testing . 34 4.1 SonarQube tool analysing some projects . 44 4.2 SonarQube vulnerability details of one project . 44 4.3 Signature of method . 45 4.4 SpotBugs for Intellij . 45 4.5 SpotBugs - Issues by severity . 45 4.6 FindSecurityBugs - Issues . 46 4.7 FindSecurityBugs - Issues by severity . 46 1 Chapter 1 Introduction 1.1 Context and motivation Nowadays, the need for a shorter time-to-market of applications is evident. However, even though the time needed for developing them gets reduced, we still need to be able to deliver reliable and secure apps. This was already a challenging task, and it is even more so with the time restrictions and the rapidly evolving technologies. Hidden flaws in software can result in secur- ity vulnerabilities that potentially allow attackers to compromise systems and applications. Some hackers and crackers may be keeping an eye on our valuable personal information. Hence, these applications need to be secured and should be reliable since our private and important information or docu- ments are stored on the back end of these n-tiered applications. Each year thousands of such vulnerabilities are reported publicly to the Common Vulner- abilities and Exposures database [23]. These vulnerabilities are often caused by subtle errors made by programmers and can propagate quickly due to the prevalence of open-source software and code reuse. We are confronted with the dilemma of the need for speeding up the soft- ware development process while at the same time the requirement of deliver- ing reliable and secure applications. There are many approaches for tackling this problem which range from adapting the software development process to more concrete technical solutions. In this TFM we will try to analyse the use of one or several automatised software tools for verifying whether the application under construction has the required level of security by detecting potential vulnerabilities or flaws that could cause an undesired misfunction. This approach addresses the detection of vulnerable code during the course of the software development cycle. 1.2 Objectives The first objective of this TFM is to propose a suitable solution for using one or many of the tools, reviewed in this document, to be incorporated in the software development cycle for improving the delivery of more reliable and secure applications, according to a set of criteria to be defined below. These Chapter 1. Introduction 2 criteria are based on the current situation of the organisation where we cur- rently work. To be able to attain the previous objective, we need to perform a profound literature study of the different tools (and kinds of tools) available in the mar- ket that can be applicable to solve the aforementioned problem. We will also search for benchmarks and comparisons of these tools to analyse their ad- vantages and disadvantages with respect to each other.
Load more

Recommended publications
  • Arxiv:2106.03271V1 [Cs.SE] 6 Jun 2021
    Noname manuscript No. (will be inserted by the editor) Fixing Vulnerabilities Potentially Hinders Maintainability Sofia Reis · Rui Abreu · Luis Cruz Received: date / Accepted: date Abstract Security is a requirement of utmost importance to produce high- quality software. However, there is still a considerable amount of vulnerabil- ities being discovered and fixed almost weekly. We hypothesize that develop- ers affect the maintainability of their codebases when patching vulnerabili- ties. This paper evaluates the impact of patches to improve security on the maintainability of open-source software. Maintainability is measured based on the Better Code Hub’s model of 10 guidelines on a dataset, including 1300 security-related commits. Results show evidence of a trade-off between secu- rity and maintainability for 41:90% of the cases, i.e., developers may hinder software maintainability. Our analysis shows that 38:29% of patches increased software complexity and 37:87% of patches increased the percentage of LOCs per unit. The implications of our study are that changes to codebases while patching vulnerabilities need to be performed with extra care; tools for patch risk assessment should be integrate into the CI/CD pipeline; computer science curricula needs to be updated; and, more secure programming languages are necessary. Keywords Software Security Software Maintenance Open-Source Software · · Sofia Reis INESC ID and IST, University of Lisbon, Lisbon, Portugal E-mail: sofi[email protected] Rui Abreu INESC ID and FEUP, University of Porto, Porto, Portugal E-mail: [email protected] arXiv:2106.03271v2 [cs.SE] 12 Sep 2021 Luis Cruz Delft University of Technology, Delft, The Netherlands E-mail: [email protected] 2 Sofia Reis et al.
    [Show full text]
  • EBOOK-Injection-Guide.Pdf
    1 INDEX What is Injection .......................................................................................................................... 5 Tainted Data Flow .................................................................................................................... 5 Injection Prevention Rules ...................................................................................................... 6 Injection Types ............................................................................................................................. 7 SQL Injection (CWE-89) ......................................................................................................... 10 LDAP Injection (CWE-90) ....................................................................................................... 13 XML Injection (CWE-91) ......................................................................................................... 15 XPath Injection (CWE-643) .................................................................................................... 16 XML External Entity Reference (XXE) (CWE-611) ................................................................ 18 Expression Language (EL) Injection (CWE-917) .................................................................. 20 OS Command Injection (CWE-78) ......................................................................................... 21 2 According to the OWASP Top 10 Application Security Risks (2017) . ... (https://www.owasp.org/index.php/Top_10-2017_Top_10),
    [Show full text]
  • Rest-Secure-Ebook.Pdf
    This document is about REST security issues and presents the main security problems that need attention, the attack threats and attack surface for REST, and how to handle some common security issues. We will center our discussion around Java-based REST frameworks, but many concepts are also valid for other implementation languages, like PHP, .Net, JavaScript, Python, Ruby … REST (REpresentational State Transfer) is an architectural style to build services on top of the Web. REST simplifies interaction with a web-based system via simplified URLs, instead of complex HTTP requests. A REST-enabled application is made of resources (“nouns“), each responding to different “verbs” (for example, HTTP methods like GET, POST, PUT, DELETE…) over well-defined URLs (typically HTTP/HTTPS URLs) which map entities in the system to endpoints. Each REST request/response to a resource uses one or more resource representation, typically negotiated between client and server (for example, using Accept and Content-Type HTTP headers). Most common representation formats include JSON, XML or raw text, with many other alternatives like YAML, Atom and HTML which are also used. Here are the main characteristics of a REST architecture style: Client-Server: a pull-based interaction style: consuming components pull representations. Stateless: each request from client to server must contain all the information necessary to understand the request, and cannot take advantage of any stored context on the server. Cache aware: to improve network efficiency, responses must be capable of being labeled as cacheable or non-cacheable. Uniform interface: all resources are accessed with a generic interface (e.g., HTTP GET, POST, PUT, DELETE).
    [Show full text]
  • FAQS-1.3.Pdf
    1. Kiuwan Basics ........................................................................................................................ 3 1.1. Where can I find useful Kiuwan resources? .................................................................. 3 1.2. What is a Kiuwan application? ...................................................................................... 3 1.3. What does Kiuwan consider a defect? .......................................................................... 3 1.4. What metrics are measured by Kiuwan? ...................................................................... 3 1.5. What programming languages are supported by Kiuwan?........................................... 4 1.6. What Quality and Security Standards are supported by kiuwan? ................................ 5 1.7. What is the Kiuwan support for SQL? ........................................................................... 5 1.8. Does Kiuwan support mobile technologies? ................................................................. 5 1.9. Does Kiuwan support Sharepoint? ................................................................................ 5 1.10. Does Kiuwan support PHP Symfony ? ....................................................................... 5 1.11. How to analyze ABAP code? ...................................................................................... 5 1.12. How to analyze OracleForms code? .......................................................................... 6 1.13. What is a Quality Model? Should I
    [Show full text]
  • Kiuwan Code Security (SAST). Sicherheitsprobleme Im Devops-Prozess Aufdecken Und Rechtzeitig Beseitigen
    Die Software-Modernisierer Kiuwan Code Security (SAST). Sicherheitsprobleme im DevOps-Prozess aufdecken und rechtzeitig beseitigen. Entlarven Sie Code-Schwachstellen Ihre Vorteile Automatische .Codescans entlarven .Sicherheits- EASIRUN PRODUCT PARTNER schwachstellen .in weni- • Verhindern Sie Probleme und gen. Minuten. Als er- Schwachstellen so früh wie möglich im schwingliche..SaaS- oder On-Premise-Lösung für DevOps-Prozess. Teams und Unternehmen jeder Größe analysiert • Analysieren Sie Ihren Code konsistent in Kiuwan Code Security (SAST) die Compliance des der gesamten Organisation mit zentral Codes nach den strengsten Sicherheitsstandards verwalteten Modellen. wie OWASP und CWE, deckt alle wichtigen Sprachen ab und lässt sich in führende DevOps-Tools • Führen Sie jedes Mal, wenn Sie Ihren integrieren. Code speichern, automatische Analysen in der IDE aus. DevOps in DevSecOps transformieren • Stellen Sie sicher, dass der gesamte Code lokal analysiert wird, bevor er an Die Einführung von DevOps ist ein Meilenstein für die das Code-Repository übergeben wird. agile Softwareentwicklung. Der DevOps-Ansatz für den Softwareentwicklungs-Lebenszyklus (SDLC) ist die • Beheben Sie Probleme und Antwort auf die Geschwindigkeit und den Erweiterbar- Schwachstellen billiger und schneller. keit, die für den Erfolg in der heutigen Umgebung er- • Erstellen Sie von Anfang an bessere forderlich sind. Software. Aber was ist mit der Sicherheit? Schließlich bestand die „alte Schule“ darin, zu warten, bis die Anwendung • Geeignet für jede Entwicklungsmethodik, fertig war und sie für Ad-hoc-Prüfungen an die Sicher- einschließlich Agile und DevOps. heitsexperten weiterzugeben. Mit den flexiblen Inte- grationsmöglichkeiten kann die Prüfung der Code- EasiRunEuropa GmbH Kiuwan Code Security Datenblatt| 1von6 Die Software-Modernisierer sicherheit ein fester Bestandteil jeder Phase des SDLC Ergebnisse der Scans sind innerhalb von Sekunden, sein.
    [Show full text]
  • Magic Quadrant for Application Security Testing
    16/09/2019 Gartner Reprint Licensed for Distribution Magic Quadrant for Application Security Testing Published 18 April 2019 - ID G00346593 - 58 min read By Analysts Ayal Tirosh, Mark Horvath, Dionisio Zumerle DevSecOps, modern web application design and high-profile breaches are expanding the scope of the AST market. Security and risk management leaders will need to meet tighter deadlines and test more complex applications by accelerating efforts to integrate and automate AST in the software life cycle. Strategic Planning Assumption By 2022, 10% of coding vulnerabilities identified by static application security testing (SAST) will be remediated automatically with code suggestions applied from automated solutions, up from less than 1% today. Market Definition/Description Gartner defines the application security testing (AST) market as the sellers of products and services designed to analyze and test applications for security vulnerabilities. Gartner identifies three main styles of AST: ■ SAST technology analyzes an application’s source, bytecode or binary code for security vulnerabilities, typically at the programming and/or testing software life cycle (SLC) phases. ■ Dynamic AST (DAST) technology analyzes applications in their dynamic, running state during testing or operational phases. It simulates attacks against an application (typically web- enabled applications and services), analyzes the application’s reactions and, thus, determines whether it is vulnerable. ■ Interactive AST (IAST) technology combines elements of SAST and DAST simultaneously. It is typically implemented as an agent within the test runtime environment (for example, instrumenting the Java Virtual Machine [JVM] or .NET CLR) that observes operation or attacks and identifies vulnerabilities. AST can be delivered as a tool or as a subscription service.
    [Show full text]
  • Controlo De Acesso Baseado Em Funç ˜Oes E Geraç ˜Ao Autom´Atica De
    UNIVERSIDADE DE LISBOA FACULDADE DE CIENCIASˆ DEPARTAMENTO DE INFORMATICA´ Gestao˜ de Acesso a Dados no Back-End: Controlo de Acesso Baseado em Func¸oes˜ e Gerac¸ao˜ Automatica´ de Relatorios´ Rui Filipe Vilac¸a Oliveira Peixoto Mestrado em Engenharia Informatica´ Especializac¸ao˜ em Engenharia de Software Versao˜ Publica´ Trabalho de Projeto orientado por: Prof. Doutora Andreia Filipa Torcato Mordido 2020 Agradecimentos Primeiramente, gostaria de agradecer a toda a minha fam´ılia, em particular: a` minha namorada, que me apoia incansavel´ e incondicionalmente; aos meus pais, que, apesar das adversidades da vida, sempre me encorajaram e ajudaram a seguir os meus sonhos; aos meus irmaos˜ pelo companheirismo e boa disposic¸ao˜ em todos os momentos; a` minha madrinha por estar sempre presente e dispon´ıvel para tudo. Um especial agradecimento tambem´ aos pais, avos´ e restante fam´ılia da minha namorada, que desde o primeiro dia me acolheram e apoiaram em todos os n´ıveis. Agradec¸o a` Faculdade de Cienciasˆ da Universidade de Lisboa e a todos os meus profes- sores, pelo rigor de ensino e todos os anos de constante aprendizagem ao longo deste percurso academico.´ Um obrigado especial a` minha orientadora, que se mostrou sem- pre interessada e sol´ıcita, desempenhando um papel deveras importante no sucesso deste projeto. Gostaria ainda de agradecer a todos os meus amigos mais proximos,´ incluindo o grupo de amigos do Secundario,´ que mesmo longe se mantem´ solido´ e unido, e aos meus colegas de licenciatura e mestrado, nomeadamente Andre,´ Paulo, Inesˆ e Micael, pelo apoio e todos os trabalhos que desenvolvemos juntos.
    [Show full text]
  • Funcionalidad De Kiuwan
    Date: 02/16/2015 Review: Feb 2015 Version Changes Feb 2015 It updates contents to Kiuwan February 2015’s release. We thank Lourdes Ortiz Saqudo, from Universidad de Huelva, for reviewing the document and detecting some errors. II CHANGES LOG ..................................................................................................................... II CONTRIBUTIONS AND ACKNOWLEDGMENTS .......................................................... II CONTENT ............................................................................................................................. III INDEX OF FIGURES ........................................................................................................... VI 1 INTRODUCTION ............................................................................................................ 1 2 KIUWAN ........................................................................................................................... 1 2.1 FUNCTIONALITIES ........................................................................................................................................... 2 2.2 TARGET USERS ............................................................................................................................................... 3 2.3 HIGHLIGHTS .................................................................................................................................................. 3 2.4 ADVANTAGES ...............................................................................................................................................
    [Show full text]
  • Insights (Sca)
    PRODUCT DATASHEET INSIGHTS (SCA) Almost every developer relies to some degree on open source software, and it’s tough to beat the flexibility of open use and distribution licensing. However, it’s also critical that all developers understand how to control open source components. There are a number of dependency, security, and license compatibility issues involved with open source solutions that require some consideration before launching an application. It is of huge importance to generate a complete and accurate inventory of all open source and third-party components used during builds or in applications. Your open source components are as much a part of your application as the code you’ve built yourself. The role, functions, features, behavior, and licensing of every open source component need to be fully understood in order to properly manage your application deployment and comply with software licensing regulations. Eliminate time consuming and error prone process of manually compiling the inventory - including their dependencies – in an effort to determine if you’re impacted by a new security vulnerability alert or to check for license issues.Draft an official policy that will cover all of the developers under your roof. KIUWAN INSIGHTS STANDS OUT No configuration needed Fully customizable – visually & conceptually Request a free demo or quote and discover how Kiuwan Insights can help you rationalize your application components SOME DETECTED VULNERABILITIES • Application Misconfiguration • Interprocess Communication • Credential/Session
    [Show full text]
  • A Comparative Case Study on Tools for Internal Software Quality Measures
    A Comparative Case Study on Tools for Internal Software Quality Measures Bachelor of Science Thesis in Software Engineering and Management MAYRA NILSSON Department of Computer Science and Engineering UNIVERSITY OF GOTHENBURG CHALMERS UNIVERSITY OF TECHNOLOGY Gothenburg, Sweden 2018 The Author grants to University of Gothenburg and Chalmers University of Technology the non-exclusive right to publish the Work electronically and in a non-commercial purpose make it accessible on the Internet. The Author warrants that he/she is the author to the Work, and warrants that the Work does not contain text, pictures or other material that violates copyright law. The Author shall, when transferring the rights of the Work to a third party (for example a publisher or a company), acknowledge the third party about this agreement. If the Author has signed a copyright agreement with a third party regarding the Work, the Author warrants hereby that he/she has obtained any necessary permission from this third party to let University of Gothenburg and Chalmers University of Technology store the Work electronically and make it accessible on the Internet. {A Comparative Case Study on Tools for Internal Software Quality Measures} {MAYRA G. NILSSON } © {MAYRA G. NILSSON}, June 2018. Supervisor: {LUCAS GREN}{VARD ANTINYAN} Examiner: {JENIFFER HORKOFF} University of Gothenburg Chalmers University of Technology Department of Computer Science and Engineering SE-412 96 Göteborg Sweden Telephone + 46 (0)31-772 1000 [Cover: Generated image based on keywords used in this
    [Show full text]
  • Conversational Code Analysis: the Future of Secure Coding Fitzroy D
    i i “conversational˙analysis˙chapter” — 2021/5/14 — 0:17 — page 1 — #1 i i This chapter was accepted on May 12, 2021 for publication in the book Coding Theory - Recent Advances, New Perspectives and Applications, IntechOpen, London Chapter 1 Conversational Code Analysis: The Future of Secure Coding Fitzroy D. Nembhard and Marco M. Carvalho Abstract The area of software development and secure coding can benefit signifi- cantly from advancements in virtual assistants. Research has shown that many coders neglect security in favor of meeting deadlines. This shortcoming leaves systems vulnerable to attackers. While a plethora of tools are available for programmers to scan their code for vulnerabilities, finding the right tool can be challenging. It is therefore imperative to adopt measures to get programmers to utilize code analysis tools that will help them produce more secure code. This chapter looks at the limitations of existing approaches to secure coding and proposes a methodology that allows programmers to scan and fix vulnerabili- ties in program code by communicating with virtual assistants on their smart devices. With the ubiquitous move towards virtual assistants, it is important to design systems that are more reliant on voice than on standard point-and-click and keyboard-driven approaches. Consequently, we propose MyCodeAnalyzer, a Google Assistant app and code analysis framework, which was designed to interactively scan program code for vulnerabilities and flaws using voice commands during development. We describe the proposed methodology, implement a prototype, test it on a vulnerable project and present our results. Keywords: secure coding, virtual assistant, code analysis, static analysis 1.
    [Show full text]
  • Are You at Risk of an Injection Attack? These Types of Attacks Are Common, Primarily Because They Affect Ubiquitous SQL Databases
    Are you at risk of an injection attack? These types of attacks are common, primarily because they affect ubiquitous SQL databases. If a user — internal or external — supplies information through a form, you may be at risk. Insufficient input validation may allow users to insert or inject their own parameters in your SQL call and gain access to some or all of your data. Injection flaws occur primarily when an application uses untrusted data when constructing an SQL call or when an application relies on older, vulnerable frameworks. An attacker can simply modify the ‗id‘ parameter in their browser to return all records. More savvy attackers can even, under the right circumstances, make changes to data. In addition to impacting SQL databases, injection flaws can also be found in queries from LDAP, XPath or NoSQL as well as OS commands, SMTP headers, XML parsers and the like. Injection flaws are most common in legacy code, but they are tough to find and eradicate during testing. You really need to examine the code manually to check for injection flaws. Injection attacks can be devastating to your business, both from a technical aspect and from the business side. Once an injection attack takes place, you can no longer trust your data. It may be corrupted or denial of access may occur. In rare cases, injection attacks can take down your entire DBMS or issue commands to your operating system. You lose the ability to guarantee confidentiality to your authorized users or customers, because sensitive information may have been made available to attackers.
    [Show full text]