DOCSLIB.ORG

Making the JDK More Secure

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Making the JDK More Secure Making the JDK More Secure Sean Mullan Oracle September 19, 2016 @seanjmullan Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Safe Harbor Statement The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 2 Agenda 1 Java Security Overview 2 Making the JDK More Secure 3 Cryptography 4 Public Key Infrastructure 5 Transport Layer Security 6 Other Areas Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 3 Java Security Overview Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 4 Java Security Overview • Java Security technology can generally be divided into three areas • Language and Runtime security controls • APIs and Libraries for integrating security into applications • Tools for managing security Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 5 Java Security Components Java Language and Runtime Security Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 6 Java Security Components JAAS GSSAPI/Kerberos XML Signature APIs and Libraries JSSE (SSL/TLS) SASL JCE (crypto) PKI Java Language and Runtime Security Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 7 Java Security Components Tools keytool jarsigner policytool kinit, klist, ktab JAAS GSSAPI/Kerberos XML Signature APIs and Libraries JSSE (SSL/TLS) SASL JCE (crypto) PKI Java Language and Runtime Security Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 8 Making the JDK More Secure Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 9 Overall Goals • Provide out-of-the box secure defaults • Restrict broken or weak cryptographic algorithms and protocols • Ensure API and tool defaults are safe to use • Provide sufficiently strong algorithms for every security function • Incorporate new security standards • Adhere to industry best practices Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 10 What does “Secure by Default” actually mean? • “Security by default, in software, means that the default configuration settings are the most secure settings possible, which are not necessarily the most user friendly settings. In many cases, security and user friendliness are evaluated based on both risk analysis and usability tests. This leads to the discussion of what the most secure settings actually are. As a result, the precise meaning of ‘secure by default’ remains undefined.” https://en.wikipedia.org/wiki/Secure_by_default Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 11 Secure by Default Challenges • Compatibility • Interoperability • Usability • One size does not fit all • Severity of issue Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 12 Crypto Roadmap http://java.com/cryptoroadmap • Publicly available roadmap of upcoming restrictions and changes to security defaults • Provides advance notice of the changes and guidance for determining if you may be affected • Also shows all changes that have been released in the past year • Does not apply to third party security providers • Initially published on August 18, 2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 13 Crypto Roadmap Planned Changes Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 14 Crypto Roadmap: Example of How to Test Changes Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 15 Crypto Roadmap Released Changes Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 16 Evolution of Java and Secure by Default • Initial focus: provide protection against untrusted code • Default sandbox policy • Enforced by a SecurityManager • As scope of security APIs expanded, new defaults became necessary • Cryptographic algorithms were weakening or being broken • TLS was increasingly under attack • Going forward, module system will introduce additional safeguards • Not just for code running with a Security Manager Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 17 MessageDigest Cryptography Data (SHA-256) Digest Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 18 Java Security Components Tools keytool jarsigner policytool kinit, klist, ktab JAAS GSSAPI/Kerberos XML Signature APIs and Libraries JSSE (SSL/TLS) SASL JCE (crypto) PKI Java Language and Runtime Security Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 19 Cryptography (JCE) Secure by Default Guidelines • Direct access to crypto algorithms (via JCE) is not restricted • Ensures long-term compatibility • Applications can still use MD2, but they do so at their own risk • Required algorithms are evaluated at each major release • Ensures every SE implementation supports industry-recommended algorithms • API and Provider defaults are changed if necessary • Stronger or new algorithms are added over time • Ideally, there should be at least one secure algorithm for each cryptographic primitive (MessageDigest, Signature, Cipher, etc) Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 20 Algorithm Requirements • Every implementation of Java SE MUST support a minimum set of security algorithms • These required algorithms improve compatibility, interoperability and security • The list is evaluated at each release. New requirements as of JDK 9: • Signature: SHA256withDSA • KeyPairGenerator (implementations must support the key size in parens): DSA (2048), DiffieHellman (2048, 4096), RSA (4096) • AlgorithmParameterGenerator: DSA (2048), DiffieHellman (2048, 4096) • Cipher: AES/GCM/NoPadding (128), AES/GCM/PKCS5Padding (128) • SSLContext: TLSv1.1, TLSv1.2 • TrustManagerFactory: PKIX • Full list is at http://download.java.net/java/jdk9/docs/technotes/guides/security/ StandardNames.html#impl Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 21 Cryptographic API and Provider Defaults • Several JCE APIs include optional parameters that default to API or implementation specific values if not specified • We periodically review these to ensure the defaults are secure. In JDK 9, we have changed the following defaults: • The default key size for the RSA and DiffieHellman KeyPairGenerator and the DiffieHellman AlgorithmParameterGenerator implementations increased from 1024 bits to 2048 bits • The default KeyStore type changed from JKS to PKCS12 • KeyStore.getDefaultType() now returns “PKCS12” • See JEP 229 for more information: http://openjdk.java.net/jeps/229 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 22 New JDK 9 Cryptographic Algorithms • SHA-3 • FIPS PUB 202 • Support for 4 variants: SHA3-224, SHA3-256, SHA3-384, SHA3-512 • Usage is exactly the same as other MessageDigest algorithms: MessageDigest md = MessageDigest.getInstance(“SHA3-256”); md.update(buffer); byte[] digest = md.digest(); • See JEP 287 for more information: http://openjdk.java.net/jeps/287 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 23 New JDK 9 Cryptographic Algorithms (continued) • DRBG SecureRandom Algorithms • DRBG = Deterministic Random Bit Generator • NIST Special Publication 800-90Ar1 • Uses modern algorithms as strong as SHA-512 and AES-256 • API can be configured with different security strengths and features to match user requirements • Implementation of all 3 mechanisms: Hash_DRBG, HMAC_DRBG, CTR_DRBG • default mechanism is Hash_DRBG, but can be changed using the securerandom.drbg.config security property • See JEP 273 for more information: http://openjdk.java.net/jeps/273 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 24 DRBG Example // Requests a strong DRBG instance with a personalization string. The // returned instance is guaranteed to support 256 bits of security // strength with prediction resistance and reseeding capability. SecureRandom drbg = SecureRandom.getInstance(“DRBG", DrbgParameters.instantiation( 256, DrbgParameters.Capability.PR_AND_RESEED, "hello".getBytes())); // Generates random bytes. Prediction resistance is not requested, but // an additional input is specified. byte[] buffer = new byte[32]; drbg.nextBytes(buffer, DrbgParameters.nextBytes(-1, false, "more".getBytes())); // Reseeds this instance. Prediction resistance is not requested, but // an additional input is specified. drbg.reseed(DrbgParameters.reseed(false, "extra".getBytes())); Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 25 Public Key Infrastructure Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 26 Java Security Components Tools keytool jarsigner policytool kinit, klist, ktab JAAS GSSAPI/Kerberos XML Signature APIs and Libraries JSSE (SSL/TLS) SASL JCE (crypto) PKI Java Language and Runtime Security Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 27 Public Key Infrastructure Secure by Default Guidelines • Restrict certificates that are signed with weak or broken algorithms or key sizes by default • Certificates are commonly used to authenticate entities over a network • Restrictions are enforced in the PKIX implementation of the CertPathValidator and CertPathBuilder
Load more

Recommended publications
  • A Java Security Scanner for Eclipse
    Colby College Digital Commons @ Colby Honors Theses Student Research 2005 JeSS – a Java Security Scanner for Eclipse Russell Spitler Colby College Follow this and additional works at: https://digitalcommons.colby.edu/honorstheses Part of the Databases and Information Systems Commons, Other Computer Engineering Commons, Programming Languages and Compilers Commons, and the Systems Architecture Commons Colby College theses are protected by copyright. They may be viewed or downloaded from this site for the purposes of research and scholarship. Reproduction or distribution for commercial purposes is prohibited without written permission of the author. Recommended Citation Spitler, Russell, "JeSS – a Java Security Scanner for Eclipse" (2005). Honors Theses. Paper 567. https://digitalcommons.colby.edu/honorstheses/567 This Honors Thesis (Open Access) is brought to you for free and open access by the Student Research at Digital Commons @ Colby. It has been accepted for inclusion in Honors Theses by an authorized administrator of Digital Commons @ Colby. JeSS – a Java Security Scanner for Eclipse Russell Spitler Senior Honors Thesis Spring 2005 Colby College Department of Computer Science Advisor: Dale Skrien Contents Chapter 1 Introduction 1 Chapter 2 Secure Coding and Java Security 2.1 – Secure Coding 3 2.2 – Java Security 7 Chapter 3 Java Security Holes 3.1 – Don’t depend on initialization 13 3.2 – Make everything final 14 3.3 – Make your code unserializable and undeserializable 16 3.4 – Make your class non-Cloneable 19 3.5 – Don’t rely on
    [Show full text]
  • Eu-19-Zhang-New-Exploit-Technique
    New Exploit Technique In Java Deserialization Attack • Yang Zhang • Yongtao Wang Keyi Li “在此键⼊引⽂。• ” • Kunzhe Chai –Johnny Appleseed New Exploit Technique In Java Deserialization Attack Back2Zero Team BCM Social Corp. BCM Social Group Who are we? Yang Zhang(Lucas) • Founder of Back2Zero Team & Leader of Security Research Department in BCM Social Corp. • Focus on Application Security, Cloud Security, Penetration Testing. • Spoke at various security conferences such as CanSecWest, POC, ZeroNights. Keyi Li(Kevin) • Master degree majoring in Cyber Security at Syracuse University. • Co-founder of Back2Zero team and core member of n0tr00t security team. • Internationally renowned security conference speaker. –Johnny Appleseed Who are we? Yongtao Wang • Co-founder of PegasusTeam and Leader of Red Team in BCM Social Corp. • Specializes in penetration testing and wireless security. • Blackhat, Codeblue, POC, Kcon, etc. Conference speaker. Kunzhe Chai(Anthony) • Founder of PegasusTeam and Chief Information Security Officer in BCM Social Corp. • Author of the well-known security tool MDK4. • Maker of China's first Wireless Security Defense Product Standard and he also is the world's first inventor of Fake Base Stations defense technology–Johnny Appleseed Agenda • Introduction to Java Deserialization • Well-Known Defense Solutions • Critical vulnerabilities in Java • URLConnection • JDBC • New exploit for Java Deserialization • Takeaways 2015: Chris Frohoff and Gabriel Lawrence presented their research into Java object deserialization vulnerabilities ultimately resulting in what can be readily described as the biggest wave of RCE bugs in Java history. Introduction to Java Deserialization Java Deserialization Serialization • The process of converting a Java object into stream of bytes. Databases Deserialization Serialization • A reverse process of creating a Java object from stream of bytes.
    [Show full text]
  • Apache Harmony Project Tim Ellison Geir Magnusson Jr
    The Apache Harmony Project Tim Ellison Geir Magnusson Jr. Apache Harmony Project http://harmony.apache.org TS-7820 2007 JavaOneSM Conference | Session TS-7820 | Goal of This Talk In the next 45 minutes you will... Learn about the motivations, current status, and future plans of the Apache Harmony project 2007 JavaOneSM Conference | Session TS-7820 | 2 Agenda Project History Development Model Modularity VM Interface How Are We Doing? Relevance in the Age of OpenJDK Summary 2007 JavaOneSM Conference | Session TS-7820 | 3 Agenda Project History Development Model Modularity VM Interface How Are We Doing? Relevance in the Age of OpenJDK Summary 2007 JavaOneSM Conference | Session TS-7820 | 4 Apache Harmony In the Beginning May 2005—founded in the Apache Incubator Primary Goals 1. Compatible, independent implementation of Java™ Platform, Standard Edition (Java SE platform) under the Apache License 2. Community-developed, modular architecture allowing sharing and independent innovation 3. Protect IP rights of ecosystem 2007 JavaOneSM Conference | Session TS-7820 | 5 Apache Harmony Early history: 2005 Broad community discussion • Technical issues • Legal and IP issues • Project governance issues Goal: Consolidation and Consensus 2007 JavaOneSM Conference | Session TS-7820 | 6 Early History Early history: 2005/2006 Initial Code Contributions • Three Virtual machines ● JCHEVM, BootVM, DRLVM • Class Libraries ● Core classes, VM interface, test cases ● Security, beans, regex, Swing, AWT ● RMI and math 2007 JavaOneSM Conference | Session TS-7820 |
    [Show full text]
  • Java Security, 2Nd Edition
    Table of Contents Preface..................................................................................................................................................................1 Who Should Read This Book?.................................................................................................................1 Versions Used in This Book....................................................................................................................2 Conventions Used in This Book..............................................................................................................2 Organization of This Book.......................................................................................................................3 What's New in This Edition.....................................................................................................................5 How to Contact Us...................................................................................................................................5 Acknowledgments....................................................................................................................................6 Feedback for the Author..........................................................................................................................6 Chapter 1. Java Application Security...............................................................................................................7 1.1 What Is Security?...............................................................................................................................7
    [Show full text]
  • Java(8$ Andrew$Binstock,$Editor$In$Chief,$Dr.Dobbs$
    Java$Update$and$Roadmap$ November(2014( Tomas$Nilsson$ Senior$Principal$Product$Manager$ Java$SE$ Copyright$©$2014,$Oracle$and/or$its$affiliates.$All$rights$reserved.$$|$ Safe$Harbor$Statement$ The$following$is$intended$to$outline$our$general$product$direcNon.$It$is$intended$for$ informaNon$purposes$only,$and$may$not$be$incorporated$into$any$contract.$It$is$not$a$ commitment$to$deliver$any$material,$code,$or$funcNonality,$and$should$not$be$relied$upon$ in$making$purchasing$decisions.$The$development,$release,$and$Nming$of$any$features$or$ funcNonality$described$for$Oracle’s$products$remains$at$the$sole$discreNon$of$Oracle.$ Copyright$©$2014,$Oracle$and/or$its$affiliates.$All$rights$reserved.$$|$ Agenda$ 1( Oracle$and$Java$ 2( Java$SE$8$Overview$ 3( Java$SE$9$and$Beyond$ Copyright$©$2014,$Oracle$and/or$its$affiliates.$All$rights$reserved.$$|$ 1( Oracle$and$Java$ 2( Java$SE$8$Overview$ 3( Roadmap$ Copyright$©$2014,$Oracle$and/or$its$affiliates.$All$rights$reserved.$$|$ Oracle$and$Java$ • Oracle$has$used$Java$since$the$beginning$of$Nme$(eg$1990s)$ • Acquired$JAVA$(Sun$Microsystems)$in$2010,$including$Java$IP,$trademarks$ • Embraced$OpenJDK,$open$community,$open$JCP$ – Welcomed$IBM,$Apple,$SAP,$ARM,$AMD,$Intel,$Twi\er,$Goldman$Sachs,$Microso^$and$many$others$ – Made$OpenJDK$official$Java$SE$reference$implementaNon$ – Ongoing$move$towards$open$development,$governance,$transparency$ • JDK$development:$Oracle$and$community$ – Oracle$focus$on$modernizaNon,$security,$big$Ncket$R&D$and$commercial$value$to$Oracle$ – Community$contributes$based$on$interest$and$ability,$examples:$
    [Show full text]
  • Evaluating the Flexibility of the Java Sandbox
    Evaluating the Flexibility of the Java Sandbox Zack Coker, Michael Maass, Tianyuan Ding, Claire Le Goues, and Joshua Sunshine Carnegie Mellon University {zfc,mmaass}@cs.cmu.edu, [email protected], {clegoues,sunshine}@cs.cmu.edu ABSTRACT should protect both the host application and machine from The ubiquitously-installed Java Runtime Environment (JRE) malicious behavior. In practice, these security mechanisms provides a complex, flexible set of mechanisms that support are problematically buggy such that Java malware is often the execution of untrusted code inside a secure sandbox. able to alter the sandbox's settings [4] to override security However, many recent exploits have successfully escaped the mechanisms. Such exploits take advantage of defects in either sandbox, allowing attackers to infect numerous Java hosts. the JRE itself or the application's sandbox configuration to We hypothesize that the Java security model affords devel- disable the security manager, the component of the sandbox opers more flexibility than they need or use in practice, and responsible for enforcing the security policy [5, 6, 7, 8]. thus its complexity compromises security without improving In this paper, we investigate this disconnect between theory practical functionality. We describe an empirical study of the and practice. We hypothesize that it results primarily from ways benign open-source Java applications use and interact unnecessary complexity and flexibility in the design and with the Java security manager. We found that developers engineering of Java's security mechanisms. For example, regularly misunderstand or misuse Java security mechanisms, applications are allowed to change the security manager at that benign programs do not use all of the vast flexibility runtime, whereas static-only configuration of the manager afforded by the Java security model, and that there are clear would be more secure.
    [Show full text]
  • 6.4.0 Release Notes
    Red Hat JBoss Enterprise Application Platform 6.4 6.4.0 Release Notes For Use with Red Hat JBoss Enterprise Application Platform 6 Last Updated: 2017-12-12 Red Hat JBoss Enterprise Application Platform 6.4 6.4.0 Release Notes For Use with Red Hat JBoss Enterprise Application Platform 6 Legal Notice Copyright © 2017 Red Hat, Inc.. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. 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, 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 Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Migration-Guide.Pdf
    Java Platform, Standard Edition Oracle JDK Migration Guide Release 12 F13815-02 March 2019 Getting Started The purpose of this guide is to help you identify potential issues and give you suggestions on how to proceed as you migrate your existing Java application to the JDK 12 release. The guide also highlights the significant changes and enhancements done to the JDK 12 release. This guide contains the following sections: • Significant Changes in the JDK • Preparing For Migration • Migrating From JDK 8 to Later JDK Releases • Next Steps Significant Changes in the JDK Before migrating your application to the latest JDK release, you must understand what the updates and changes are between it and the previous JDK release. If you are migrating from JDK 8, you should also be familiar with the differences between JDK 8 and later releases that are described in Migrating From JDK 8 to Later JDK Releases. See the following sections to know some of the significant changes in latest JDK releases. Significant Changes in JDK 12 Release The following are some of the important additions and updates in Java SE 12 and JDK 12: • JVM Constants API is introduced to model nominal descriptions of key class-file and run-time artifacts, in particular constants that are loadable from the constant pool. See JVM Constant API. • The switch statement is extended so that it can be used either as a statement or an expression. This is a preview language feature. See JEP 325: Switch Expressions (Preview) and JEP 12: Preview Language and VM Features. 1 • Support for Unicode 11.0.
    [Show full text]
  • The Java® Virtual Machine Specification Java SE 11 Edition
    The Java® Virtual Machine Specification Java SE 11 Edition Tim Lindholm Frank Yellin Gilad Bracha Alex Buckley Daniel Smith 2018-08-21 Specification: JSR-384 Java SE 11 (18.9) ("Specification") Version: 11 Status: Final Release Specification Lead: Oracle America, Inc. ("Specification Lead") Release: September 2018 Copyright © 1997, 2018, Oracle America, Inc. All rights reserved. The Specification provided herein is provided to you only under the Limited License Grant included herein as Appendix A. Please see Appendix A, Limited License Grant. Table of Contents 1 Introduction 1 1.1 A Bit of History 1 1.2 The Java Virtual Machine 2 1.3 Organization of the Specification 3 1.4 Notation 4 1.5 Feedback 4 2 The Structure of the Java Virtual Machine 5 2.1 The class File Format 5 2.2 Data Types 6 2.3 Primitive Types and Values 6 2.3.1 Integral Types and Values 7 2.3.2 Floating-Point Types, Value Sets, and Values 8 2.3.3 The returnAddress Type and Values 10 2.3.4 The boolean Type 10 2.4 Reference Types and Values 11 2.5 Run-Time Data Areas 11 2.5.1 The pc Register 12 2.5.2 Java Virtual Machine Stacks 12 2.5.3 Heap 13 2.5.4 Method Area 13 2.5.5 Run-Time Constant Pool 14 2.5.6 Native Method Stacks 14 2.6 Frames 15 2.6.1 Local Variables 16 2.6.2 Operand Stacks 17 2.6.3 Dynamic Linking 18 2.6.4 Normal Method Invocation Completion 18 2.6.5 Abrupt Method Invocation Completion 18 2.7 Representation of Objects 19 2.8 Floating-Point Arithmetic 19 2.8.1 Java Virtual Machine Floating-Point Arithmetic and IEEE 754 19 2.8.2 Floating-Point Modes 20 2.8.3 Value
    [Show full text]
  • Java (Software Platform) from Wikipedia, the Free Encyclopedia Not to Be Confused with Javascript
    Java (software platform) From Wikipedia, the free encyclopedia Not to be confused with JavaScript. This article may require copy editing for grammar, style, cohesion, tone , or spelling. You can assist by editing it. (February 2016) Java (software platform) Dukesource125.gif The Java technology logo Original author(s) James Gosling, Sun Microsystems Developer(s) Oracle Corporation Initial release 23 January 1996; 20 years ago[1][2] Stable release 8 Update 73 (1.8.0_73) (February 5, 2016; 34 days ago) [±][3] Preview release 9 Build b90 (November 2, 2015; 4 months ago) [±][4] Written in Java, C++[5] Operating system Windows, Solaris, Linux, OS X[6] Platform Cross-platform Available in 30+ languages List of languages [show] Type Software platform License Freeware, mostly open-source,[8] with a few proprietary[9] compo nents[10] Website www.java.com Java is a set of computer software and specifications developed by Sun Microsyst ems, later acquired by Oracle Corporation, that provides a system for developing application software and deploying it in a cross-platform computing environment . Java is used in a wide variety of computing platforms from embedded devices an d mobile phones to enterprise servers and supercomputers. While less common, Jav a applets run in secure, sandboxed environments to provide many features of nati ve applications and can be embedded in HTML pages. Writing in the Java programming language is the primary way to produce code that will be deployed as byte code in a Java Virtual Machine (JVM); byte code compil ers are also available for other languages, including Ada, JavaScript, Python, a nd Ruby.
    [Show full text]
  • A Security Policy Oracle: Detecting Security Holes Using Multiple API Implementations
    A Security Policy Oracle: Detecting Security Holes Using Multiple API Implementations Varun Srivastava Michael D. Bond Kathryn S. McKinley Vitaly Shmatikov Yahoo! The Ohio State University The University of Texas at Austin varun [email protected] [email protected] fmckinley,[email protected] Abstract 1. Introduction Even experienced developers struggle to implement security poli- Demand for secure software is increasing, but ensuring that soft- cies correctly. For example, despite 15 years of development, stan- ware is secure remains a challenge. Developers are choosing dard Java libraries still suffer from missing and incorrectly applied memory-safe systems [9, 39] and languages such as Java and permission checks, which enable untrusted applications to execute C# in part because they improve security by reducing memory- native calls or modify private class variables without authorization. corruption attacks. Even memory-safe systems, however, rely on Previous techniques for static verification of authorization enforce- the access-rights model to ensure that the program has the appro- ment rely on manually specified policies or attempt to infer the pol- priate permissions before performing sensitive actions. Unfortu- icy by code-mining. Neither approach guarantees that the policy nately, even experienced developers find it difficult to specify and used for verification is correct. implement access-rights policies correctly. Consequently, semantic In this paper, we exploit the fact that many modern APIs have mistakes—such as missing permission checks which enable mali- multiple, independent implementations. Our flow- and context- cious code to bypass protection—have become a significant cause sensitive analysis takes as input an API, multiple implementations of security vulnerabilities [26].
    [Show full text]
  • Security Issue with JRE 1.7.0 51
    Security Issue with JRE 1.7.0_51 Issue With recent version of Java release 1.7.0_51 users encounter security warning messages, when signed applets are run within Internet Explorer. In such environments, customers using ISD 11.2 and earlier versions might see the following Warnings or error messages. 1. This application will be blocked in a future Java security update because the JAR file manifest does not contain the Permissions attribute. Please contact the Publisher for more information. 2. java.lang.SecurityException: Missing required Permissions manifest attribute in main jar: http://demo.com/ISD/websignsunjvm.jar Fix The security warning issue can be solved by following any one of the following two fixes. First one is a work around solution and the second one involves updating the websignsunjvm.jar (which has all the required entries to overcome security warning). Fix 1 Adding the domain name of the web site hosting ISD WebSign Java applet to trusted list of Java Plug-in will resolve this issue. Follow the steps below to 1. Open Java Control Panel Applet (Start->Programs->Control Panel-> Java). 2. Go to Security Tab and click on Edit Site List... Button under Exception Site List section. 3. Click on Add button to enter the location e.g. http://demo.com/ (is the domain or server name where the applet is hosted or published) and click on OK button. Adding non HTTPS sites might show some warning messages, ignore them. 4. Next step is to clean the Plug-in cache. Go To General tab, click on Setting button under Temporary Internet Files and click on delete files.
    [Show full text]