Internet DRAFT - draft-msahni-lamps-ocsp-nonce
draft-msahni-lamps-ocsp-nonce
LAMPS M. Sahni, Ed.
Internet-Draft Palo Alto Networks
Intended status: Standards Track April 3, 2020
Expires: October 5, 2020
OCSP Nonce Extension
draft-msahni-lamps-ocsp-nonce-03
Abstract
This document specifies the updated format of the Nonce extension in
Online Certificate Status Protocol (OCSP) request and response
messages. OCSP is used to check the status of a certificate and the
Nonce extension is used in the OCSP request and response messages to
avoid replay attacks. This document updates the RFC 6960
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 5, 2020.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Sahni Expires October 5, 2020 [Page 1]
Internet-Draft OCSP Nonce Extension April 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
2. OCSP Extensions . . . . . . . . . . . . . . . . . . . . . . . 2
2.1. Nonce Extension . . . . . . . . . . . . . . . . . . . . . 3
3. Security Considerations . . . . . . . . . . . . . . . . . . . 4
3.1. Replay Attack . . . . . . . . . . . . . . . . . . . . . . 4
3.2. Nonce Collision . . . . . . . . . . . . . . . . . . . . . 4
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5. Changes to Appendix B. of RFC 6960 . . . . . . . . . . . . . 4
5.1. Changes to Appendix B.1. OCSP in ASN.1 - 1998 Syntax . . 4
5.2. Changes to Appendix B.2 OCSP in ASN.1 - 2008 Syntax . . . 5
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Normative References . . . . . . . . . . . . . . . . . . 5
6.2. Informative References . . . . . . . . . . . . . . . . . 6
6.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
This document updates the usage and format of the Nonce extension
used in OCSP request and response messages. This extension was
previously defined in the section 4.1.1 of [RFC6960]. The [RFC6960]
does not mention any minimum and maximum length of the nonce
extension. Due to not having an upper or lower limit of the length
of the Nonce extension, the OCSP responders that follow [RFC6960] may
be vulnerable to various attacks like Denial of Service attacks
[RFC4732], chosen prefix attacks to get a desired signature from the
OCSP responder and possible evasions that can use the Nonce extension
data for evasion. This document specifies a lower limit of 1 and
upper limit of 32 to the length of the Nonce extension. This
document updates the [RFC6960].
1.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
2. OCSP Extensions
The message format for the OCSP request and response is defined in
the [RFC6960]. It also defines the standard extensions for OCSP
messages based on the extension model employed in X.509 version 3
certificates (see [RFC5280]). Following is the list of standard
Sahni Expires October 5, 2020 [Page 2]
Internet-Draft OCSP Nonce Extension April 2020
extensions that can be used in the OCSP messages by the OCSP
responder and OCSP client.
* Nonce
* CRL References
* Acceptable Response Types
* Archive Cutoff
* CRL Entry Extensions
* Service Locator
* Preferred Signature Algorithms
* Extended Response Definition
This document only specifies the new format for Nonce extension and
does not change specification of any of the other standard
extensions.
2.1. Nonce Extension
This section updates the Section 4.4.1 [1] of [RFC6960] which
describes the OCSP Nonce extension.
The nonce cryptographically binds a request and a response to prevent
replay attacks. The nonce is included as one of the
requestExtensions in requests, while in responses it would be
included as one of the responseExtensions. In both the request and
the response, the nonce will be identified by the object identifier
id-pkix-ocsp-nonce, while the extnValue is the value of the nonce.
If Nonce extension is present then the length of nonce MUST be
atleast 1 octet and can be upto 32 octets.
A server MUST reject any OCSP request having a Nonce extension with
length of more than 32 octets with the malformedRequest
OCSPResponseStatus as described in section 4.2.1 of [RFC6960]
The minimum nonce length of 1 octet is defined to provide the
backward compatibility with clients following [RFC6960]. However the
newer OCSP clients MUST use length of atleast 16 octets for Nonce
extension and the value of the nonce MUST be generated using a
cryptographically strong pseudorandom number generator.
id-pkix-ocsp OBJECT IDENTIFIER ::= { id-ad-ocsp }
id-pkix-ocsp-nonce OBJECT IDENTIFIER ::= { id-pkix-ocsp 2 }
Nonce ::= OCTET STRING(SIZE(1..32))
Sahni Expires October 5, 2020 [Page 3]
Internet-Draft OCSP Nonce Extension April 2020
3. Security Considerations
The security considerations of OCSP in general are described in the
[RFC6960]. The Nonce extension is used to avoid replay attacks
during the interval in which the previous OCSP response for a
certificate is not expired but responder has a changed status for
that certificate. Including client's Nonce value in the OCSP
response makes sure that the response is a latest response from the
server and not an old copy.
3.1. Replay Attack
The Nonce extension is used to avoid replay attacks. Since the OCSP
responder may choose to not send the Nonce extension in the OCSP
response even if the client has sent the Nonce extension in the
request [RFC5019], a man in the middle (MITM) entity can intercept
the OCSP request and respond with a earlier response from the server
without the Nonce extension. This can be mitigated by server using a
closer nextUpdate value in the OCSP response.
3.2. Nonce Collision
If the value of the nonce used by a client is not random enough, then
the attacker may pre fetch responses with the predicted nonce and can
replay them, thus defeating the purpose of using nonce. Therefore
the client MUST use a nonce value that contains cryptographically
strong randomness and is freshly generated. Also if the length of
the nonce is very small e.g. 1 octet then attacker can pre fetch
responses with all the possible vaule of nonce and replay a matching
nonce. A client SHOULD use 32 octets for the nonce length.
4. IANA Considerations
This document does not include any new media type registrations
for OCSP.
5. Changes to Appendix B. of RFC 6960
This section updates the ASN.1 definitions of the OCSP Nonce
extension in the Appendix B.1 and Appendix B.2 of the [RFC6960] The
appendix B.1 defines OCSP using ASN.1 - 1998 Syntax and appendix B.2
defines OCSP using ASN.1 - 2008 Syntax
5.1. Changes to Appendix B.1. OCSP in ASN.1 - 1998 Syntax
OLD Syntax:
Sahni Expires October 5, 2020 [Page 4]
Internet-Draft OCSP Nonce Extension April 2020
The definition of OCSP Nonce Extension is not provided in the
Appendix B.1 of [RFC6960] for the ASN.1 - 1998 Syntax.
NEW Syntax:
Nonce ::= OCTET STRING(SIZE(1..32))
5.2. Changes to Appendix B.2 OCSP in ASN.1 - 2008 Syntax
OLD Syntax:
re-ocsp-nonce EXTENSION ::= { SYNTAX OCTET STRING IDENTIFIED
BY id-pkix-ocsp-nonce }
NEW Syntax:
re-ocsp-nonce EXTENSION ::= { SYNTAX OCTET STRING(SIZE(1..32))
IDENTIFIED BY id-pkix-ocsp-nonce }
6. References
6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", DOI 10.17487/RFC8174, RFC 8174, BCP 14,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,
Housley, R., and W. Polk, "Internet X.509 Public Key
Infrastructure Certificate and Certificate Revocation List
(CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, May 2008,
<https://www.rfc-editor.org/info/rfc5280>.
[RFC6960] Santesson, S., Myers, M., Ankney, R., Malpani, A.,
Galperin, S., and C. Adams, "X.509 Internet Public Key
Infrastructure Online Certificate Status Protocol - OCSP",
RFC 6960, DOI 10.17487/RFC6960, June 2013,
<https://www.rfc-editor.org/info/rfc6960>.
Sahni Expires October 5, 2020 [Page 5]
Internet-Draft OCSP Nonce Extension April 2020
6.2. Informative References
[RFC4732] Handley, M., Ed., Rescorla, E., Ed., and IAB, "Internet
Denial-of-Service Considerations", RFC 4732,
DOI 10.17487/RFC4732, December 2006,
<https://www.rfc-editor.org/info/rfc4732>.
[RFC5019] Deacon, A. and R. Hurst, "The Lightweight Online
Certificate Status Protocol (OCSP) Profile for High-Volume
Environments", RFC 5019, DOI 10.17487/RFC5019, September
2007, <https://www.rfc-editor.org/info/rfc5019>.
6.3. URIs
[1] https://tools.ietf.org/html/rfc6960#section-4.4.1
Author's Address
Mohit Sahni (editor)
Palo Alto Networks
Email: msahni@paloaltonetworks.com
Sahni Expires October 5, 2020 [Page 6]
