Reporting protocol vulnerabilities to the IETF

The IETF recognizes that security vulnerabilities will be discovered in IETF protocols and welcomes their critical evaluation by researchers.

Such research keeps the Internet safe. If you believe you’ve discovered a protocol vulnerability, we very much welcome your contribution.

Remediation of vulnerabilities is typically started through disclosure to an open and public IETF working group or mailing list where protocol improvements can be discussed. If you do not know which IETF working group or mailing list to use, or that does not seem appropriate for your work, we invite you to contact <protocol-vulnerability@ietf.org> (link to PGP key below) for assistance.

A full explanation of the IETF processes related to disclosure and remediation of vulnerabilities is documented below.

The IETF does not pay “bug bounties” for reported vulnerabilities.

Scope

The IETF is a standards development organization that publishes RFCs that describe Internet protocols and specifications. Internet-Drafts (I-Ds) are working documents used in the creation of RFCs. RFCs and I-Ds are collectively referred to as documents. While documents include an occasional reference or example source code, the IETF does not build or maintain implementations of protocols.

Design vulnerabilities or security issues with operational practices described in IETF documents can be addressed in the IETF.  Implementation or configuration vulnerabilities in products, open source projects, or services that may implement these documents need to be addressed by their corresponding vendor or maintainers.  The IETF does not have a formal means to reach these parties. 

Additionally, the IETF does not certify conformance of products to its published documents.

Vulnerabilities in any infrastructure and services that support the IETF, IRTF and IAB (such as those associated with the ietf.org, iab.org, irtf.org and rfc-editor.org domains) are the responsibility of the IETF Administration LLC who has their own vulnerability disclosure policy.

IETF Reponse to Vulnerability Reports

The IETF values your critical analysis of its work.  What the IETF will do with your vulnerability report depends on the type of document where the issue is found, the severity of the issue, the complexity of the mitigation, and the maturity of the document in question.

  • For published RFCs (files named RFC####), these are completed, community reviewed documents.  If the working group that produced the RFC is still active, it will work to vet the issue with you and decide the appropriate way to address the issue.  If confirmed, the vulnerability might be addressed via an errata, an updated protocol specification document, or an entire new document to handle the issue.  For closed working groups, the severity of the issue will determine the next steps.  Minor issues can be covered with errata.  For more significant updates, the corresponding Area Directors may charter a new working group to address the issues or individually sponsor an update.
  • For working group Internet-Drafts (files named draft-ietf-XXX-YYY), these are documents adopted for consideration by an IETF working group but are not yet finalized. The issue should be raised on the associated working group mailing list. The associated working group will work to vet the issue with you and come to a consensus on how to resolve the issue after notification. (see activity #9 of Figure 1)
  • For individual Internet-Draft submissions (files named draft-ZZZ-AAA), these are not officially adopted documents in the IETF.  Such documents were submitted for consideration by the IETF for adoption by their author(s).  Any issues found should be discussed with the authors (see Activity #7 of Figure 1).  Despite not being formally adopted, a working group may be tracking or discussing such documents.  Therefore, discussion of the issue may be appropriate on the working group mailing list.  Note that there are rare instances where a document with this naming convention is adopted by a working group or is being advanced to publication as an RFC without being submitted to a working group (i.e., individual submission).  

Vulnerabilities found in working group Internet-Drafts or individual submission documents that have expired, or were fixed in subsequent versions; or published RFCs that are marked historic, are unlikely to have action taken on them. Additionally, as the RFC series predates the IETF and not all RFCs are the result of IETF standards activity — some even document proprietary protocols not developed in the IETF. These may also not have action taken in response to a vulnerability report.

Generally speaking, being available for follow-up clarifications and related discussions posed by the Area Directors, Working Group Chairs, working group participants, or document authors is extremely helpful. 

The IETF does not pay “bug bounties” for reported vulnerabilities.

Reporting a Vulnerability

A vulnerability report related to IETF documents can be sent to the <protocol-vulnerability@ietf.org> (link to PGP key below) and the Security Area Directors will make a best effort to triage and action the information. This email alias does not have a public archive. If explicitly requested by the vulnerability reporter, information about the reporter can be removed when the Area Directors forward along the vulnerability information to public mailing list(s) (as noted below in the “Transparency in the IETF” and Activity #10 of Figure 1).

However, because of the distributed organization of IETF work, consulting Figure 1 can help expedite issues being reported. No vulnerability is the same and, depending on the maturity and circumstances of a given document, the reporting path will vary. Each activity in Figure 1 is documented below.

Protocol Vulnerability Reporting Guidance Figure
Vulnerability Reporting Flow

1. Is the document known?

Can the specific document in which the vulnerability is present be identified?  All IETF documents are published in the IETF Datatracker.

2. What is the document name?

What is the name of the document in which the vulnerability is present?  Published documents have the naming convention of RFCxxxx (where xxxx is a four digit number).  Internet-Drafts adopted by a working group have a naming convention of draft-ietf-xxx-yyy (where xxx is the working group in which the work is being done; and yyy is the chosen filename).  Individual submissions, drafts that are not adopted by a working group are named draft-ZZZ-AAA (where ZZZ is typically the document submitter's name). See Section 7 of Guidelines to Authors of Internet-Drafts for additional background on naming of IETF documents.

3. Is there an active working group on the topic?

Consult the list of active working groups. 

4. Is this a working group document and is it still active?

To determine if an document named ABC was produced by a working group and if this working group is active:

  • Goto https://datatracker.ietf.org/doc/ABC/
  • Click the “Status” tab
  • In the “Document” meta-data section, find the “Type” field.  There will be text for the form "Was draft-XXX (YYY WG)" or "Was draft-XXX (individual in ZZ area)".
    • Clicking on the “YYY WG” link will bring up the associated working group page and confirm if it is still active
    • Presence of the text "individual" in this field confirms that this RFC was not produced by a working group, but an individual submission.

If the originating working group is found not to be active, also review the list of active working groups per Activity #3.  A number of protocol maintenance work groups (e.g., LAMPS to address the maintenance of PKI specifications; TCPM to address TCP maintenance) have been established to update older, widely used protocols.

5. Is the “YYY” WG still active?

The procedure is the same as for Activity #4.

6. Can the vulnerability be mitigated/addressed with minor text edits or clarifications?

Judging “minor text edits or clarifications” is subjective.  Generally speaking a “minor” edit meets the definition of an errata that is meant ‘to fix "bugs" in the specification and should not be used to change what the community meant when it approved the RFC.’

7. Contact the document authors

The contact information for all authors can be found at the end of each document. Be advised, contact information is not updated after the document is published so it may be out-of-date.

8. File Errata

Errata for published RFCs can be filed at https://www.rfc-editor.org/errata.php.

9. Contact the WG mailing list

Send your vulnerability report to the appropriate, public WG mailing list.  To determine the mailing list of a working group named YYY identified in Activity #3 or 4.

Note that the mailing list name might not be the same as the working name.

For anything sent to a WG list, also consider sending a CC: to the general reporting alias, <protocol-vulnerability@ietf.org> (link to PGP key below), to provide additional visibility to the Security Area Directors.

10. Contact the general alias

As a last resort, vulnerability reports can always be sent to the <protocol-vulnerability@ietf.org> (link to PGP key below) and the Security Area Directors will make a best effort to triage and action the information.

Secure Communication

Encrypted messages using the PGP key (local | key-server) with a fingerprint of 5674 EB6C DC18 5E2A 3D7A 56E5 AB78 AE3D 1772 9268 can be sent to <protocol-vulnerability@ietf.org>