DOCSLIB.ORG

Secure Coding Practices in Java: Challenges and Vulnerabilities

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Secure Coding Practices in Java: Challenges and Vulnerabilities Secure Coding Practices in Java: Challenges and Vulnerabilities Na Meng Stefan Nagy Daphne Yao Wenjie Zhuang Gustavo Arango Argoty Virginia Tech Blacksburg, Virginia 24060 {nm8247,snagy2,danfeng,kaito,gustavo1}@vt.edu ABSTRACT 1 INTRODUCTION Java platform and third-party libraries provide functionalities to fa- Java platform and third-party libraries or frameworks (e.g., Boun- cilitate secure coding. However, misusing these functionalities can cyCastle [6]) provide various features to enable secure coding. Mis- cost developers tremendous time and effort, or introduce security using these libraries and frameworks not only slows development vulnerabilities in software. Prior research focused on the misuse of time, but also leads to security vulnerabilities in the resulting soft- cryptography and SSL APIs, but did not explore the fundamental re- ware [14, 98, 99, 103]. search question: what are the biggest challenges and vulnerabilities Prior research mainly focused on cryptography and SSL API in secure coding practices? In this paper, we conducted a broader misuse causing security vulnerabilities [80, 82, 85, 88]. Specifically, empirical study on StackOverflow posts to understand developers’ Lazar et al. manually examined 269 published cryptographic vul- concerns on Java secure coding, their programming obstacles, and nerabilities in the CVE database, and observed 83% of them resulted the potential vulnerabilities in their code. from cryptography API misuse [88]. Nadi et al. further investigated We observed that developers have shifted their effort to the usage the obstacles introduced by Java cryptography APIs, developers’ of authentication and authorization features provided by Spring usage of the APIs, and desired tool support [94]. Fahl et al. [82] and Security—a third-party framework designed to secure enterprise Georgiev et al. [85] separately implemented a man-in-the-middle applications. The programming challenges are all related to APIs or attack, and detected vulnerable Android applications and software libraries, including the complicated cross-language data handling libraries misusing SSL APIs. Despite these studies, it is still un- of cryptography APIs, and the complex Java-based or XML-based known what the major concerns are in secure coding practices, approaches to configure Spring Security. More interestingly, we and whether these practices benefitted from security research over identified security vulnerabilities in the suggested code of accepted time. answers. The vulnerabilities included using insecure hash functions In this paper, we conducted a broader in-depth investigation on (e.g., MD5), breaking SSL/TLS security through bypassing certificate the common concerns, programming challenges, and security vul- validation, and insecurely disabling the default protection against nerabilities in developers’ secure coding practices by inspecting 503 Cross Site Request Forgery attacks. Our findings reveal the insuffi- StackOverflow (SO) posts related to Java security. We chose SO[63] ciency of secure coding assistance and documentation, as well as because (1) it is a popular online platform for developers to share the gap between security theory and coding practices. and discuss programming issues and solutions, and (2) SO plays an important role in educating developers and shaping their daily CCS CONCEPTS coding practices. The main challenge of conducting this empirical study is interpreting security-relevant programming issues or solu- • General and reference → Empirical studies; tions within both program and security contexts. To comprehend each post within the program context, we manually checked all KEYWORDS included information related to the source code, configuration files, CSRF, SSL/TLS certificate validation, cryptographic hash functions, and/or execution environments. Then, we identified the root causes authentication, authorization, StackOverflow posts and solutions of each problem. To comprehend each post within the security context, we collected information about the developers’ ACM Reference format: implementation intents and the involved security libraries, and Na Meng Stefan Nagy Daphne Yao Wenjie Zhuang Gustavo determined whether the final implementation fulfilled the intents. Arango Argoty. 2018. Secure Coding Practices in Java: Challenges and Such manual analysis requires so much expertise in both software Vulnerabilities. In Proceedings of ACM conference, Gothenburg, Sweden, May engineering and security that it is difficult to automate. 2018 (ICSE’18), 13 pages. In our thorough manual analysis of the 503 posts, we investigated https://doi.org/10.475/123_4 the following three research questions (RQs): RQ1 What are the common concerns in Java secure coding? Al- Permission to make digital or hard copies of part or all of this work for personal or though there are various security libraries and frameworks [2, classroom use is granted without fee provided that copies are not made or distributed 32, 34, 57, 86, 95], we do not know which libraries and func- for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for third-party components of this work must be honored. tionalities are most frequently asked about by developers. For all other uses, contact the owner/author(s). RQ2 What are the common programming challenges? We aim to ICSE’18, May 2018, Gothenburg, Sweden identify the common obstacles preventing developers from © 2018 Copyright held by the owner/author(s). easily and correctly implementing secure code. Such infor- ACM ISBN 123-4567-24-567/08/06. https://doi.org/10.475/123_4 mation will provide SE researchers actionable knowledge to ICSE’18, May 2018, Gothenburg, Sweden Na Meng Stefan Nagy Daphne Yao Wenjie Zhuang Gustavo Arango Argoty better develop tools, and help close the gap between intended cryptographic operations (encryption, digital signatures, hashes), versus actual library usage. generators or converters of cryptographic material (keys and algo- RQ3 What are the common security vulnerabilities? We aim to rithm parameters), or objects (keystores or certificates) that encap- identify security the vulnerabilities spread on SO, since their sulate the cryptographic data. gaining popularity may cause insecure code to see wide- The access control architecture protects the access to sensitive re- spread implementation. This effort will help raise security sources (e.g., local files) or sensitive application code (e.g., methods consciousness among software developers. in a class). All access control decisions are mediated by a security In our study, we made three major observations. manager. By default, the security manager uses the AccessController • There were security vulnerabilities in the recommended code class for access control operations and decisions. of some accepted answers. For example, usage of MD5 or Secure communication ensures that the data which travels across SHA-1 algorithms was repeatedly suggested, although these a network is sent to the appropriate party, without being modified algorithms are notoriously insecure and should not be used. during the transmission. Cryptography forms the basis for secure Additionally, many developers were advised to trust all in- communication. The Java platform provides API support for stan- SSL/TLS HTTPS coming SSL/TLS certificates as a temporary fix to certificate dard secure communication protocols like . , or verification errors. Such action completely disrupts the secu- “HTTP secure”, is an application-specific implementation that isa rity of SSL. Although this bad practice was initially reported combination of HTTP and SSL/TLS. by researchers in 2012 [82, 85], developers have still asked for and accepted it until now. Furthermore, when encounter- 2.2 Java EE Security ing errors in implementing Spring Security authentication, Java EE is an standard specification for enterprise Java extensions [44]. developers were often suggested a workaround to blindly Various application servers are built to implement this specification, disable the default security protection against Cross Site such as JBoss or WildFly [71], Glassfish [18], WebSphere [69], Request Forgery (CSRF) attacks. and WebLogic [3]. A Java EE application consists of components • Various programming challenges were related to security li- deployed into various containers. The Java EE security specification brary usage. For instance, developers became stuck using defines that containers secure components by supporting features cryptography APIs due to clueless error messages, complex like authentication and authorization. cross-language data handling, and delicate implicit API usage In particular, authentication defines how communicating en- constraints. However, when using Spring Security, develop- tities, such as a client and a server, prove to each other that they ers struggled with the two alternative ways of configuring are who they say they are. An authenticated user is issued a creden- security: Java-based or XML-based. tial, which includes user information like usernames/passwords or • Since 2012, developers have increasingly relied on Spring Se- tokens. Authorization ensures that users have permissions to per- curity for secure coding. 267 of the 503 examined posts (53%) form operations or access data. When accessing a certain resource, were about Spring Security. However, to the best of our a user is authorized if the server can map this user to a security knowledge, research has not yet investigated
Load more

Recommended publications
  • Spring Roo - Reference Documentation
    Spring Roo - Reference Documentation DISID CORPORATION S.L. Table of Contents Getting started . 1 1. Overview . 2 2. What’s new in Spring Roo 2.0 . 3 Improved extensibility . 3 No backward compatibility . 3 Usability improvements . 3 Centered in Spring technologies . 3 Application architecture . 4 Domain model . 4 View layer . 4 3. Requirements . 6 4. Install Spring Roo . 7 Using Spring Roo . 9 5. The Roo shell . 10 6. Impatient beginners . 12 7. Create your Spring Boot application . 13 8. Configure the project settings . 14 9. Setup the persistence engine . 15 10. The domain model . 16 JPA entities . 16 DTOs . 20 11. The data access layer . 21 Spring Data repositories . 21 Default queries . 21 12. The service layer . 22 Service API and Impl . 22 13. The view layer . 23 Thymeleaf view engine . 23 Spring MVC Controllers . 23 Spring Webflow . 25 14. The integration layer . 26 REST API . 26 WS API . 26 Email . ..
    [Show full text]
  • Course Title
    "Charting the Course ... ... to Your Success!" Spring 3x Advanced Topics Course Summary Description This course is the next step in using the many features Spring 3.x has to offer. Web topics covering Web Flow and MVC address the powerful features for building popular workflow structures in applications today. Spring Batch addresses the Web counterpart to business processing. The final two topics address all areas in Spring. Security touches all layers of a business application. The newly rewritten Spring Security structure covers all areas addressed down to the Method level. Spring Roo is the last topic that can be used to build entire applications, including Spring MVC. Due to the size of Spring Roo, the depth will depend on available remaining time. The various Spring Integration features of messages will be demonstrated based on student requirements. Objectives At the end of this course, students will be able to: Design, create and debug Spring MVC applications. Understand Web Flow and where it can be used. Create, monitor, and test Spring Batch applications. Apply Security to all levels of Spring applications, including methods. Use Spring Roo to create Spring applications. Configure Spring using Java Classes. Apply Spring Integration options. Topics Working with Spring Web Flow Introducing Spring Security The Web Module and Spring MFC Web Security Controllers and Commands Securing the Service Layer Binding and Validation Customizing and Extending Spring Security Introducing Spring Batch Working with Remote Services
    [Show full text]
  • Adding Red Hat Decision Manager Users 44
    Red Hat Decision Manager 7.11 Integrating Red Hat Decision Manager with other products and components Last Updated: 2021-07-06 Red Hat Decision Manager 7.11 Integrating Red Hat Decision Manager with other products and components Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Spring Framework II Course Summary
    "Charting the Course ... ... to Your Success!" Spring Framework II Course Summary Description This course is the next step in using the many features the Spring Framework has to offer. In depth Web topics covering Web Flow and MVC address the powerful features for building popular workflow structures in applications. Spring Security will be applied to all areas including the Method level. Spring ROO will be used to build entire applications, including Spring MVC. Web Services for SOAP and RESTful are included to complete the Web Tier. Objectives At the end of this course, students will be able to: Design, create and debug complex Spring MVC applications. Understand Web Flow and where it can be used. Create, monitor, and test Spring Web Services. Apply Security to all levels of Spring Framework applications, including methods. Use Spring Roo to create Spring Framework applications. Configure Spring Framework using Java Classes and eliminate Web.XML configuration. Incorporate JQuery and JavaServer Faces. Topics Web Development Spring Roo Web Services What’s Next in Spring III Security Audience This course is designed for Developers who have attended the “Spring Framework I” class or equivalent experience in developing or maintaining Spring Framework Web applications. Prerequisites Spring programming experience, a basic knowledge of configuration, familiarity with the Spring Framework dependency injection, and Aspect oriented programming. Duration Five Days Due to the nature of this material, this document refers to numerous hardware and software products by their trade names. References to other companies and their products are for informational purposes only, and all trademarks are the properties of their respective companies.
    [Show full text]
  • Spring Security Reference
    Spring Security Reference 4.2.8.RELEASE Ben Alex , Luke Taylor , Rob Winch , Gunnar Hillert Copyright © 2004-2015 Copies of this document may be made for your own use and for distribution to others, provided that you do not charge any fee for such copies and further provided that each copy contains this Copyright Notice, whether distributed in print or electronically. Spring Security Reference Table of Contents .............................................................................................................................................. xvii I. Preface ................................................................................................................................... 1 1. Getting Started ............................................................................................................... 3 2. Introduction .................................................................................................................... 4 2.1. What is Spring Security? ..................................................................................... 4 2.2. History ................................................................................................................ 6 2.3. Release Numbering ............................................................................................. 6 2.4. Getting Spring Security ........................................................................................ 7 Usage with Maven ............................................................................................
    [Show full text]
  • Spring Security
    Spring Security Reference Documentation Ben Alex Luke Taylor Spring Security: Reference Documentation by Ben Alex and Luke Taylor 3.0.8.RELEASE Spring Security Table of Contents Preface ...................................................................................................................................... x I. Getting Started ....................................................................................................................... 1 1. Introduction ................................................................................................................... 2 1.1. What is Spring Security? ..................................................................................... 2 1.2. History ................................................................................................................ 4 1.3. Release Numbering ............................................................................................. 4 1.4. Getting Spring Security ....................................................................................... 5 Project Modules ................................................................................................. 5 Core - spring-security-core.jar .................................................. 5 Web - spring-security-web.jar ..................................................... 5 Config - spring-security-config.jar ........................................... 5 LDAP - spring-security-ldap.jar ................................................ 5 ACL - spring-security-acl.jar
    [Show full text]
  • SAP Process Mining by Celonis
    TABLE OF CONTENTS REVISION HISTORY 4 INTRODUCTION 5 ABOUT THIS GUIDE 5 TARGET AUDIENCE 5 TECHNICAL CONFIGURATION – SYSTEM LANDSCAPE 8 SINGLE-SERVER DEPLOYMENT 8 MULTI-SERVER DEPLOYMENT (SCALE-OUT) 9 TECHNICAL CONFIGURATION – FILE SYSTEM LAYOUT 9 WINDOWS SYSTEMS 10 LINUX SYSTEMS 12 TECHNICAL CONFIGURATION – MULTI-SERVER 13 TECHNICAL CONFIGURATION – SECURITY 15 GENERAL SECURITY 15 SECURE COMMUNICATION BETWEEN CENTRAL APPLICATION AND COMPUTE SERVICE 17 PYTHON SECURITY 18 TECHNICAL CONFIGURATION – HIGH AVAILABILITY (HA) 19 TECHNICAL CONFIGURATION – LOGGING 21 LOGGING FOR SAP PROCESS MINING BY CELONIS 21 APPLICATION SERVER ADMINISTRATION 24 REQUIRED TOOLS 24 SAP PROCESS MINING BY CELONIS CONFIGURATION 24 SAP PROCESS MINING BY CELONIS AS OPERATING SYSTEM SERVICE 25 PERIODICAL TASKS – ARCHIVING FILES 26 SAP PROCESS MINING BY CELONIS LOG FILES 26 MIGRATION FROM SAP PROCESS MINING BY CELONIS FROM A VERSION BELOW 4.5 TO A VERSION INCLUDING AND ABOVE 4.5 30 SAP PROCESS MINING BY CELONIS CONFIGURATION STORE BACKUPS 32 © 2020 Celonis SE OPERATION GUIDE 2 RECOVERING FROM A BACKUP FOR INTEGRATED CELONIS CONFIGURATION STORE 33 BACKUP AND RECOVERY – BACKUP ANALYTICS DATABASE (SAP HANA) 34 INCLUDED MONITORING FUNCTIONALITY 35 SOFTWARE CHANGE MANAGEMENT 38 SOFTWARE UPDATE PROCEDURE 39 SUPPORT DESK MANAGEMENT 40 SLD REGISTRATION 40 CONFIGURABLE HELP PAGES 40 © 2020 Celonis SE OPERATION GUIDE 3 REVISION HISTORY VERSION NUMBER VERSION DATE SUMMARY OF REVISIONS MADE 1.4 MAR 22, 2017 Application Version 4.2 1.6 FEB 23, 2018 Updated version for application version 4.3 1.9 FEB 03, 2019 Updated version for application version 4.5 1.10 MAY 17, 2020 Updated version for application version 4.5 SP3 1.11 JUN 20, 2020 Updated version for application version 4.6 © 2020 Celonis SE OPERATION GUIDE 4 INTRODUCTION ABOUT THIS GUIDE SAP Process Mining by Celonis is a powerful software for retrieving, visualizing and analyzing real as-is business processes from transactional data stored by the SAP ERP systems.
    [Show full text]
  • Getting Started with Roo
    Getting Started with Roo Getting Started with Roo Josh Long and Steve Mayzak Beijing • Cambridge • Farnham • Köln • Sebastopol • Tokyo Getting Started with Roo by Josh Long and Steve Mayzak Copyright © 2011 Josh Long and Steve Mayzak. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Editor: Mike Loukides Cover Designer: Karen Montgomery Production Editor: Jasmine Perez Interior Designer: David Futato Proofreader: O’Reilly Production Services Illustrator: Robert Romano Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trademarks of O’Reilly Media, Inc. Getting Started with Roo, the image of the common tree kangaroo, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc. was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information con- tained herein. ISBN: 978-1-449-30790-5 [LSI] 1312551620 Table of Contents Preface ..................................................................... vii 1. Your First Intrepid Hops … err, Steps .....................................
    [Show full text]
  • Spring Roo in Action by Ken Rimple, Srini Penchikala
    MANNING Ken Rimple Srini Penchikala FOREWORD BY BEN ALEX Spring Roo in Action by Ken Rimple, Srini Penchikala Chapter 10 Copyright 2012 Manning Publications brief contents PART 1STARTING SPRING APPS RAPIDLY WITH ROO...................1 1 ■ What is Spring Roo? 3 2 ■ Getting started with Roo 25 PART 2DATABASES AND ENTITIES ........................................... 55 3 ■ Database persistence with entities 57 4 ■ Relationships, JPA, and advanced persistence 93 PART 3WEB DEVELOPMENT...................................................125 5 ■ Rapid web applications with Roo 127 6 ■ Advanced web applications 156 7 ■ RIA and other web frameworks 173 8 ■ Configuring security 189 PART 4INTEGRATION ...........................................................209 9 ■ Testing your application 211 10 ■ Enterprise services—email and messaging 243 11 ■ Roo add-ons 266 12 ■ Advanced add-ons and deployment 296 vii viii BRIEF CONTENTS PART 5 ROO IN THE CLOUD...................................................321 13 ■ Cloud computing 323 14 ■ Workflow applications using Spring Integration 337 Enterprise services— email and messaging This chapter covers Roo support for enterprise services Asynchronous messaging using a JMS topic Email service Asynchronous messaging using a JMS queue Monitoring messaging activity In the previous two chapters, you secured your Roo application by adding the Spring Security API to the application architecture mix, and you learned how to enrich the web tier of the Roo application so it’s functional from a business stand­ point. In addition to robust security features and a rich user interface, a real-world application also requires services such as customer email notification and offline data processing that occurs outside of your main business operations, where your customers receive notifications about results at a later time. In this chapter, we discuss the integration that the Roo framework provides for email and asynchronous messaging using the Java Message Service (JMS) API.
    [Show full text]
  • Spring Security Reference
    Spring Security Reference 4.2.6.RELEASE Ben Alex , Luke Taylor , Rob Winch , Gunnar Hillert Copyright © 2004-2015 Copies of this document may be made for your own use and for distribution to others, provided that you do not charge any fee for such copies and further provided that each copy contains this Copyright Notice, whether distributed in print or electronically. Spring Security Reference Table of Contents .............................................................................................................................................. xvii I. Preface ................................................................................................................................... 1 1. Getting Started ............................................................................................................... 3 2. Introduction .................................................................................................................... 4 2.1. What is Spring Security? ..................................................................................... 4 2.2. History ................................................................................................................ 6 2.3. Release Numbering ............................................................................................. 6 2.4. Getting Spring Security ........................................................................................ 7 Usage with Maven ............................................................................................
    [Show full text]
  • CELEBRATING JAVA@25 the Everlasting Age of “Write Once, Run
    The Everlasting Age of “Write Once, Run Anywhere” CELEBRATING JAVA@25 Your App Ecosystem | Driven by Java | Accelerated with Low-Code Copyright © 2020, WaveMaker, Inc. This document is not for public distribution. All rights reserved. Abstract It takes a second to sow a seed, years to create a forest, and decades to build an ecosystem. Witnessing the Java community grow everyday is a fascinating experience in itself. Many of us have lived through the launch and wide-spread adoptionof Java and we continue to witness its evolution. 25 years ago, James Gosling and others at Sun Microsystems launched the Java programming language in 1995. The driving force behind creating Java was to build an architecture-neutral, platform-independent language for software embedded in electronic devices. Since then it has evolved into an ecosystem, from the Java Virtual Machine (JVM) to Jakarta EE (Java EE). To keep up with enterprise demands, the new focus of the Java ecosystem is on cloud computing with the aim of providing complete control and flexibility to accelerate application development in the cloud. Enriched layer upon layer, Java as a language has evolved over the decades and has created a special connection with many professional developers. In this eBook, find out how Java is shaping the present and future technology, how it has evolved, the applications of Java and why it is popular, and how it forms the backbone of modern applications and is used to meet the modern enterprise demands. Copyright © 2020, WaveMaker, Inc. This document is not for public distribution. All rights reserved. Table of Contents Introduction 1 How Java is shaping present and future technology Java is still young @25 2 The Evolution Over the Decades 3 Applications of Java and Why it is Popular 4 Combine the Old with New Technology Meet the Demands of the Modern Enterprise 5 The Future of Java and How it is Evolving Copyright © 2020, WaveMaker, Inc.
    [Show full text]
  • Did You Remember to Test Your Tokens?
    Did You Remember To Test Your Tokens? Danielle Gonzalez Michael Rath Mehdi Mirakhorli Rochester Institute of Technology DLR Institute of Data Science Rochester Institute of Technology Rochester, NY, USA Technical University Ilmenau Rochester, NY, USA [email protected] Jena / Ilmenau, Germany ABSTRACT With complexity comes risk, especially for security features; Authentication is a critical security feature for confirming the iden- broken authentication is second in OWASP’s Top 10 Most Critical tity of a system’s users, typically implemented with help from Web Application Security Risks [48]. Hence, the importance of testing frameworks like Spring Security. It is a complex feature which complex & critical security features is clear. The most common should be robustly tested at all stages of development. Unit testing security testing techniques, penetration and functional testing [31], is an effective technique for fine-grained verification of feature are “black-box”: performed on running instances of a system with behaviors that is not widely-used to test authentication. Part of no knowledge of the source code. However, there is an established the problem is that resources to help developers unit test security “white-box” (code available) technique that can be applied much features are limited. Most security testing guides recommend test sooner, before a prototype is even ready: unit testing. cases in a “black box" or penetration testing perspective. These Unfortunately, unit tests are often overlooked for security [9]; resources are not easily applicable to developers writing new unit traditional definitions [22] imply that unit tests have limited scope. tests, or who want a security-focused perspective on coverage.
    [Show full text]