Security Now
Security is top-of-mind everywhere, especially right here where Juniper experts share their thoughts on the latest security breakthroughs and product advancements
Showing results for 
Search instead for 
Do you mean 

FAQ: Protecting your OpenSSL Server from HeartBleed using IDP

by Juniper Employee ‎04-11-2014 05:10 PM - edited ‎04-17-2014 10:36 AM

Updated 4/15/14: Included Link to Affected Juniper Products

Updated 4/17/14: Included new IDP signature covering Client and STARTTLS Vector




Chances are, you've read a few hundred blog posts already on CVE-2014-0160, OpenSSL SSL/TSL/DTSL Heartbeat Information Disclosure - aka the Heartbleed bug.


The good news is, most Juniper products are not affected.  SRX was amongst those not affected, and therefore is in a good position to help.  For a complete list of affected products and the fixes for them, please Folow This Link.


Even better news?  Juniper's IDP signature team has already written a signature to block the attack.


Word has gotten out about the new sig, but there's been some confusion over it, so this blog post will serve as a central clearing house for those frequently asked questions and their answers.




Q: Does Juniper have a signature for this issue?

A: YES!  It is "SSL: OpenSSL TLS DTLS Heartbeat Information Disclosure", which was released April 8, 2014 at 9:50 p.m PDT in signature export 2362.  It is classified as a "High" or "Major" (depending on your management system) severity attack.  It is also flagged as a performance-impacting ("slow") signature (more on that in a bit).


The "Short Name" for this signature is:




Q: How does the signature work?

A: The signature checks for over-large Heartbeat packets for all versions of SSL/TSL/DTLS.


Q: Isn't that cheating?

A: Yes, it is.  The correct way to detect this behavior would be to compare the "Record Length" value to the HeartBeat header's "Payload Length" value.  A check for an appropriate mismatch between these two headers would detect all possible attack permutations.  


Unfortunately, doing math is not our signature language's strong suit, and it can't do comparisons between values found in traffic.  A Protocol Anomaly Attack Object, however, can.  These are special checks coded directly into the decoder or the engine.  The bad news:  A Protocol Anomaly generally takes anywhere from 1 to 6 months (sometimes even longer!) to be added.  The signature works well for the time being.


Q: No False Positives?

A: None we've seen so far.


Q: What about False Negatives?

A: We've tried to be as comprehensive as we can with the signature, and as strict as possible, without generating false positives.  There are some corner cases, however that could get through.  We'd like to hope we've minimized them.  


So far, every report of False Negative presented to us has been shown to be a mistake of the tool in question, or a problem with the policy configuration.  There are some special things to keep in mind to ensure you have this signature in your policy - it won't generally automatically be there.


Q: Are you protecting clients as well?

A: Regretfully no [*YES! See update below!].  This signature has some performance issues (more on that in a bit) checking in the Client-to-Server direction, but they are manageable.  The performance impact in the Server-To-Client direction, however, is very large.  Considering the current focus on server issues with this vulnerability, the decision was made to limit the performance impact by also limiting the direction. 


Q: What about STARTTLS connections?

A: Another regret [*YES! See update below!].  Right now, we're focused on protecting native SSL/TLS/DTLS-based servers from attack.  We're looking into the possiblity of adding support to STARTTLS-protected services, but we're still very concerned about the performance impact.  Look for more signatures soon.


Q: I *am* looking for this signature!  Where the @#$% is it?!?

A: Due to our legacy dynamic grouping mechanisms in both NSM and Space SD, this signature isn't where you'd normally expect to find it.  It's been flagged as "Performance Impacting" (aka "Slow") and therefore is filtered out of the normal Recommended groups like [Recommended]SSL - Major and similar.  


"Slow" signatures are relegated to the "Misc_" appended groups, so the most specific dynamic group that contains this signature would be [Recommended]Misc_SSL - Major.


Two other techniques to ensure this signature is in your policy would be:


1. Make a custom dynamic group using the filters:  Recommended = Yes + Category = SSL  and then add that custom dynamic group to your policy.

2. Explicitly add the signature by "Short Name" to your policy without using a group:




*** Client and STARTTLS Protection Update:


An alternate signature has been released with signature update 2365 that also covers the Client direction and also adds support for STARTTLS sessions under certain circumstances.  This signature is not to be used in conjunction with the previous signature, it is an alternative that should only be used in very specific circumstances.  Its general use is not recommended.


This signature is considerably more performance impacting than the exisiting signature.  


There are also higher chances of potential false positives with this alternate signature.


For the majority of customers requiring protection of their servers from attack, this alternate signature is not necessary.


If you are experiencing possible false-negatives with the existing signature for server protection, this alternate signature will not resolve your issue.  Please ensure you have the signature in your policy using the above Q&A information, and if you are still experiencing false-negatives, please contact JTAC as soon as possible with your report.  Please have packet captures ready so we can confirm the issue rapidly.


The alternate signature is called "SSL: OpenSSL TLS DTLS Heartbeat Information Disclosure (Server, Client, and STARTTLS Support)" and its Short Name is:




This signature has been marked as "Slow" and also has NOT been marked as "Recommended".    In order to add it to your policy, you will need to add it by specifically name, as it will not be included in any predefined recommended group.


In order to apply this signature to your STARTTLS connections, you will need to adjust the application binding within your policy to ensure you cover the ports you need to cover - by default, the signature will only cover SSL-native sessions.


Please consider your environment very carefully before attempting to use this alternative signature - most customers do not need it.




Here at Signature HQ, we're committed to bringing you the freshest, most reliable, most relevant signatures we can, as quickly as possible.  


We appreciate the opportunity and the responsibility you entrust us with as your signature provider.  Please feel free to contact us through your local Juniper Representative for any signature concerns you have.

by barnet
on ‎04-21-2014 09:32 AM

I suppose either Heartbleed signature can be effective only if SSL inspection is enabled and properly set up in the IDP, right? Thanks, and kudos for a great post.

by Juniper Employee
‎04-21-2014 09:53 AM - edited ‎04-21-2014 09:54 AM

Thanks for the Kudos!


The IDP module needs to be licensed and activated in your policy, naturally.  Adding SSL-based signatures to the IDP policy automatically turns on the necessary detector needed to make that inspection happen, so no other configuration should be necessary.


Since the standard signature is designed to only protect servers, it's best used in a policy that's been crafted to inspect traffic destined to your DMZ, Data Center, or Server Farm where such servers would be located.  A zone-based policy, with clearly defined zones for the source and destination, is the best way to make that happen.


While it's not necesarily a "bad" idea to apply this to your out-bound client traffic, the signature is performance impacting. The likelihood of a random user on your client network being an attacker out to the internet is pretty low, I'd wager, and perhaps not worth the performance impact you'd get by inspecting such traffic.  


In the end, of course, local security departments need to make the right decisions for their organization.  We strive to provide those teams the best options to choose from that we can.

by Distinguished Expert
on ‎04-27-2014 10:37 AM



Since the heartbleed communication occurs outside the encrypted channel you don't need to be inspecting ssl streams for the signatures to successfully detect and block these hijacking attempts.



Juniper Networks Technical Books
About the Author
  • Andrew is a Juniper Distinguished Engineer responsible for the architecture of Juniper's network management user interfaces.
  • Amy James is Product Marketing lead for Security at Juniper Networks. She brings her knowledge of cyber security from companies like FireEye, Cisco and Cloudmark with deep roots in technology storytelling.
  • Asher Langton is a senior software engineer and malware researcher on Juniper's Sky ATP team.
  • Aviram Zrahia is a consulting engineer at Juniper Networks and an industry researcher of cyberspace. He holds a CISSP and GCIH certifications, as well as a bachelor's degree in computer science and MBA in management of technology, innovation, and entrepreneurship. He is also a research fellow in the Blavatnik Interdisciplinary Cyber Research Center (ICRC) at Tel Aviv University, currently focusing on the domain of threat intelligence sharing.
  • Brad Minnis, CPP is the Senior Director of Corporate Environmental, Health, Safety & Security for Juniper Networks, Inc. based in Sunnyvale, CA, where he is responsible for strategic design, implementation and management of the company’s security, safety, environment, crisis management and business continuity functions. He also leads the company’s efforts in corporate citizenship and sustainability, and manages the Corporation’s government-related security programs. Mr. Minnis has over 30 years experience in the Silicon Valley and has managed EHSS operations for a number of high tech companies, including Juniper Networks, 3Com Corporation, and National Semiconductor Corporation. Mr. Minnis’ specialties include security management, supply chain and product integrity, anti-counterfeit, occupational health and safety and crisis management. In his role as Cyber Incident Response Team Leader for Juniper, Mr. Minnis has managed numerous high impact cyber-related incidents and cross-functional responses. Mr. Minnis served for ten years in the United States Navy and has served in leadership positions the International Security Management Association (ISMA) and ASIS International, serving as Chairman of the San Francisco Chapter in 2003. He has also co-written several publications on software integrity assurance and supply chain security with organizations such as SAFECode. Mr. Minnis is certified as a Protection Professional by the Professional Certification Board of ASIS International and attended the University of Connecticut, where he received two certificates in Environmental, Health and Safety
  • Bill is the Director of Federal Certifications and Policy at Juniper Networks. In this role, Bill focuses on several areas unique to the needs of Federal Government customers, including product certifications, IPv6, and security. Bill came to Juniper Networks in January 2008 after more than 20 years in the IT community working with commercial enterprise customers, service providers, and the US Federal Government. Bill started his career as an engineering officer in the US Air Force after graduating with a Bachelor of Aerospace Engineering from the Georgia Institute of Technology. Bill has an MBA from the Wharton School at the University of Pennsylvania.
  • Craig Dods is the Chief Architect for Security within Juniper Networks' Strategic Verticals. He currently maintains multiple top-level industry certifications including his JNCIE-SEC, holds multiple networking and security-related patents, as well as having disclosed multiple critical-level CVE's in a responsible manner. Prior to joining Juniper, Craig served as IBM's Managed Security Services' Chief Security Architect, and held previous security roles at Check Point Software Technologies and Nokia.
  • François Prowse is a Senior Systems Engineer for Juniper Networks, based in Brisbane Australia. Francois joined Juniper in 2006 as part of the New Zealand SE team, subsequently relocating to Australia. Prior to Juniper, Francois worked for four years at Alcatel in both operational and architectural roles, being jointly responsible for the construction of New Zealands' largest MPLS core network. Prior to Alcatel, Francois worked at UUnet, focusing on core network expansion in Europe. In all previous roles JUNOS has been the driving factor behind day to day operations, providing him with over 8 years of operational experience. Francois is a Juniper Networks Certified Internet Expert (JNCIE #144) which he obtained prior to joining Juniper Networks.
  • Greg Sidebottom is a Senior Engineering Manager in the Identity and Policy Management business unit at Juniper Networks. Greg has spent the last decade plus conceptualizing, architecting, designing, and leading the implementation of Juniper's SDX and SRC families of policy based service management applications. Previous to this, Greg held positions in the software and networking industries at Siemens, Cognos, Nortel, GTE labs subsidiary MPR Teltech, and the Alberta Research Council. Greg is an author of eight invention disclosures resulting in two patents issued and three pending. Greg holds a B.Sc. in Computer Science for the University of Calgary and an M.Sc. and Ph.D. in Computing Science from Simon Fraser University.
  • Jennifer Blatnik is vice president of cloud, security and enterprise portfolio marketing at Juniper Networks with focus on enterprise deployments of security, routing, switching, and SDN products, as well as cloud solutions. She has more than 20 years of experience helping enterprises solve network security challenges. Before joining Juniper, Jennifer served multiple roles at Cisco Systems, Inc., including directing product management for security technologies aimed at small to medium enterprises, as well as supporting managed services, cloud service architectures and go-to-market strategies. She holds a B.A. in Computer Science from University of California, Berkeley.
  • Jim Kelly, Senior Product Line Manager – CTP Products Juniper Networks. Jim Kelly is the senior product line manager for the CTP products where he is responsible for the CTP product direction, marketing and circuit emulation applications within Juniper Networks. Mr. Kelly has more than 28 years of experience in the networking industry in technical roles, sales, marketing, and product management positions. He started his career in the United States Air Force. He has worked for Wang, Digital Telecom Systems, American Airlines, Network Equipment Technologies, Carrier Access, and Nortel Networks. He started Juniper Networks federal DoD sales in July 2000 and joined Juniper Networks again in October 2005 through the acquisition of Acorn Packet Solutions where he was the director of sales and marketing.
  • I have been in the networking industry for over 35 years: PBXs, SNA, Muxes, ATM, routers, switches, optical - I've seen it all. Twelve years in the US, over 25 in Europe, at companies like AT&T, IBM, Bay Networks, Nortel Networks and Dimension Data. Since 2007 I have been at Juniper, focusing on solutions and services: solving business problems via products and projects. Our market is characterized by amazing technological innovations, but technology is no use if you cannot get it to work and keep it working. That is why services are so exciting: this is where the technology moves out of the glossy brochures and into the real world! Follow me on Twitter: @JoeAtJuniper For more about me, go to my LinkedIn profile:
  • Kevin Walker is the Security Chief Technology and Strategy Officer for Juniper’s Development and Innovation (JDI) organization. He is responsible for driving the security strategy both internally within Juniper, and externally with investors, partners, influencers, and customers. He provides the guidance required for JDI to conceive, develop and create momentum for industry-leading security solutions. Working closely with the Security Engineering team, Walker identifies the opportunities for improved security, growth, and innovation to deliver the scalable, reliable, and compliant security architecture needed in today’s security landscape. Before joining Juniper, Walker was VP and Assistant Chief Information Security Officer (CISO) at He has served as a Chief Information Security Officer (CISO), Chief Security Strategist and Director of Information Security across a number of notable companies including Intuit, Cisco, Symantec and VERITAS Software. With over twenty-five years in various computer science and information technology disciplines, focusing on enterprise applications, network design, and information security, Walker possesses research and engineering expertise across of range of technologies including networking protocols, securing applications at the atomic level, cryptography, and speech biometrics.
  • Security Life timer, who has been described as a true IT security ‘guru’. It is certainly apt: his knowledge and expertise developed over the course of more than 20 years in IT have helped many customers implement a security strategy that not only safeguards their business and information, but enables Digital Transformation. A noted public speaker on security issues, Lee’s passion and style stand out in the sometimes staid world of network security. Prior to joining Juniper Networks, Lee held a number of business and technical roles at Dr Solomon’s, McAfee, Hewlett Packard, Nokia Siemens Networks and Citrix. Lee leads the Juniper Networks security business across Europe, Middle East and Africa. In this role, Lee is responsible for the company’s commercial development in the field.
  • Laurence is passionate about technology, particularly cyber security. His depth and breadth of knowledge of the dynamic security landscape is a result of over twenty years’ experience in cyber security. He understands the security concerns businesses face today and can bring insight to the challenges they will face tomorrow. Laurence joined Juniper Networks in 2016 and is our senior security specialist in EMEA. Security throughout the network is a key area where Juniper Networks can help as business moves to the cloud and undertakes the challenge of digital transformation.
  • 30 Years in Book Publishing, 20 years in Technical Book Publishing, including Apple Developer Press, Adobe Press, Nokia Developer Books, Palm Books, and since 2001, almost 10 years as consulting editor/editor in chief for Juniper Networks Book. Joined the company and started the Day One book line and in 2011, the new This Week book line.
  • Paul Obsitnik is Vice President of Service Provider Marketing for Juniper Networks Platform Systems Division (PSD), responsible for the marketing of Juniper’s portfolio of high performance routing, switching, and data center fabric products to Service Providers globally. Paul's team is responsible for marketing strategy, product marketing, go-to-market planning, and competitive analysis worldwide for the Service Provider segment. Obsitnik has extensive experience in marketing, sales and business development positions with a proven track record in creating technology markets. He has served in senior marketing and sales management positions at several companies including BridgeWave Communications, ONI Systems, NorthPoint Communications and 3Com. Paul holds a Bachelor of Science with Honors in Electrical Engineering from the United States Naval Academy and a Master of Business Administration from the Harvard Graduate School of Business. Obsitnik is based in Sunnyvale, California.
  • Solutions Marketing Sr Manager
  • Michel Tepper is a Juniper consultant and instructor working for Westcon Security in the Netherlands. He started working in ICT in 1987. Michel is also is a Juniper Ambassador. Currently he holds three Junos Professional certifications and a number of specialist and associate certifications on non-Junos tracks. Michel is an active member of J-Net and, where he uses the nickname screenie referring to the ScreenOS with which he started his Juniper Journey.
  • Scott is the Director of Product Marketing for Mobile Security at Juniper Networks. In his 20+ years in high tech, Scott has worked on Mobile and Endpoint Security, Network Security, IPS, Managed Services, Network Infrastructure, Co-location, Microprocessor Architecture, Unix Servers and Network Adapters. He has held leadership roles at Check Point, McAfee, Symantec, Exodus Communications, Cable & Wireless, Savvis, and HP.
  • Sherry Ryan is IT Vice President and CISO of Juniper Networks. Previously, Sherry held similar positions at Blue Shield of California, Hewlett-Packard, Safeway and Levi Strauss where she established and led their information security programs. Sherry holds the Certified Information Security Manager (CISM) certification from ISACA and the Certified Information Systems Security Professional (CISSP) certification from ISC2. She is a member of the High Tech Crime Investigation Association (HTCIA) and the Information Systems Security Association (ISSA). Sherry has a bachelor's degree in Business Administration from the University of Redlands, and earned her MBA from the College of Notre Dame.
About Security Now

Discussing a wide range of topics impacting enterprises and
data center security.

Subscribe RSS Icon

Our Bloggers

Kevin Walker
Vice President
Security CTSO, Engineering

Profile | Subscribe

Ritesh Agrawal
Software Engineering

Profile | Subscribe

Scott Emo
Product Marketing

Profile | Subscribe

Bill Shelton
Director Field Sales

Profile | Subscribe