资源 · 41

协调漏洞披露:接收、修复和通知

构建安全的外部报告渠道,评估影响,协调受影响方并发布实用指南。

已更新 · 16 min

虚构的无人网络安全实验室,琥珀色灯光照亮深色工作台上的设备箱和网络面板。 由人工智能生成的编辑插图

本指南有助于实现的目标

  • 确保报告的可行性和安全性。
  • 为每份报告指定负责人。
  • 协调可验证的修复。
  • 为用户提供可操作的指导。

快速检查

  • 是否可以在没有客户帐户的情况下发送报告?
  • 范围和允许的测试是否明确?
  • 如果主要联系人不在,由谁负责回复?
  • 哪些产品和供应商存在此缺陷?
  • 哪些临时缓解措施有效?
  • 该建议是否明确指出实际受影响的版本?

分步指南

  1. 1

    发布清晰的策略

    说明范围、应避免的测试、联系渠道、有用的报告详情和响应流程。 请根据您的实际情况审核该策略。

    交付成果:已发布的策略和监控渠道。

  2. 2

    确认并保护证据

    确认收到证据,分配标识符,限制敏感信息的传播,并仅要求提供重现问题所需的证据。

    交付成果:注明日期并指定负责人的报告。

  3. 3

    评估并扩大范围

    在不损害系统的情况下重现问题。 检查可利用性、资产、版本、数据以及与其他产品或供应商共享的组件。

    交付成果:影响评估和利益相关者地图。

  4. 4

    协调补救措施

    与报告者和维护者保持定期沟通。 商定验证里程碑,并根据风险或传播方式的变化调整沟通方式。

    交付成果:共享时间表、修复和回归测试。

  5. 5

    发布并跟进

    说明受影响的版本、修复或缓解措施、用户操作和不确定性。 验证部署情况,并根据实际情况更新建议。

    交付成果:版本化建议和分发证据。

虚构示例

示例情境

一位研究人员报告了旧版 API 中的访问控制故障。 团队确认了该故障,并在授权环境中重现了该问题,发现一个共享组件影响了两个产品。

决策及预期证据

该计划将维护者、版本、修复测试和临时缓解措施联系起来。 最终建议为用户提供了明确的操作步骤,并按照约定对研究人员给予了认可。

管理指标

指标衡量内容首要行动
已追踪收据报告包含所有者和首次响应日期修复静默渠道
已确定范围已确认受影响的产品、版本和依赖项在最终建议前扩大搜索范围
已验证修复已在已发布版本上重现原始案例和相关案例不要关闭存在漏洞的变体
已通知用户已向受影响用户提供指导已更新所需渠道和翻译

常见错误

  • 不考虑风险而承诺单一截止日期
  • 向报告者索取过多个人数据
  • 将确认视为补救措施
  • 在提供可用缓解措施之前发布详细的利用证据
  • 忽略合作伙伴嵌入的版本

常见问题解答

披露政策是否等同于漏洞赏金?

否。政策解释了如何报告和协调。 奖励需要单独的规则和资源。

沟通是否必须始终等待问题解决?

否。时机取决于风险、临时措施和受影响方。 记录并重新审视决策。

协调员何时应该提供帮助?

当多个供应商受到影响、联系人无响应或共享时间表难以制定时,协调员可以提供帮助。

参考资料:数据、用途与局限

文档核查日期 .

此语言版本的详细参考说明以英语提供。

参考资料:数据、用途与局限
来源与目的已核实的数据或指标使用方法需要保留的局限
CVE Program

Link discussions to the same vulnerability record.

A JSON schema defines the CVE record format. An identifier and the published contents of its record are distinct things. Open the record and references; check its state, described affected versions and supplier information. Keep the identifier in action tracking.

深入了解方法 →

A CVE identifier is neither a severity score nor proof that your installation is affected.

security.txt 与漏洞披露

此语言版本的详细参考说明以英语提供。

security.txt: find a reporting channel and check its context

A researcher may find a flaw without finding the right recipient. A security.txt file makes reporting channels and disclosure policies easier to discover. Its value then depends on monitored contacts, current information and a process that connects the report to the affected product.

This reference explains the format described in RFC 9116, an IETF Informational publication dated April 2022. The eight fields below are those defined by that RFC, rather than an exhaustive list of later extensions. Examples are fictional, using .example domains reserved for documentation. This page retrieves, validates, signs and publishes no real security.txt file.

虚构的无人网络安全实验室,琥珀色灯光照亮深色工作台上的设备箱和网络面板。 由人工智能生成的编辑插图
A fictional empty disclosure coordination laboratory. This scene depicts neither an actual facility nor evidence of security.

Six discovery and publication checks

Six discovery and publication checks
CheckRFC 9116 reference pointUseful record
LocationFor a web service, publish at /.well-known/security.txt. If both root and well-known files exist, use the well-known version.Retrieved URL, response and any difference from /security.txt at the root.
TransportRetrieve using HTTPS with HTTP 1.0 or later; referenced web URIs also use HTTPS.Certificate check and retrieval result, separately from checks of the file’s fields.
FormatUTF-8 plain text; Content-Type text/plain with charset=utf-8. Each field occupies its own line.Received header, observed encoding and a dated copy of the text examined.
ScopeThe file applies to the domain or IP address in its retrieval URI; parent domains and subdomains are not inherited automatically.Exact host, affected product and scope explained in the linked policy.
RedirectsA redirect may be legitimate but needs further inspection. The RFC recommends keeping a record.Redirect chain, host changes and the reason for using an external provider.
MaintenanceExpires is mandatory. Contacts, links and keys need to remain accessible and controlled by the organisation.Publication owner, verification date and a local review deadline before expiry.

Eight fields defined by RFC 9116

Eight fields defined by RFC 9116
FieldPresence and repetitionUseful interpretationPitfall
ContactRequired; one or more occurrences.Contact URI, such as mailto: or an HTTPS page. Occurrences should follow the publisher’s preference order.An email address without mailto: is not a conforming Contact URI. Publishing a channel does not establish that it is monitored.
ExpiresRequired; exactly one occurrence.RFC 3339 timestamp after which the data is stale and should not be used. A date less than one year ahead is recommended.That recommendation is neither a mandatory one-year duration nor a vulnerability remediation deadline.
CanonicalOptional; may repeat.Canonical URIs where the file is published. If the retrieval URI is absent from these fields, the RFC recommends not trusting the contents.Listing several Canonical URIs does not authenticate every listed host. An additional trust mechanism remains useful.
EncryptionOptional; may repeat.URI locating an encryption key; the key itself must not appear in this field.The referenced key is not necessarily the file’s signing key. Its presence proves neither authenticity nor that a report was encrypted.
PolicyOptional; may repeat.Link to the disclosure policy: scope, reporting practices and conditions explained by the organisation.The file does not replace that policy or by itself define a reward, response deadline or testing permission.
Preferred-LanguagesOptional; at most one occurrence, containing at least one language.Comma-separated language tags with equal priority regardless of order. If absent, English may be assumed.fr, en does not prioritise French. Several Preferred-Languages lines do not replace a single list.
AcknowledgmentsOptional; may repeat.Link to a page recognising people who helped remediate vulnerabilities.Coordinate public credit; it does not authorise premature disclosure of flaw details.
HiringOptional; may repeat.Link to the organisation’s security-related vacancies.Do not confuse a hiring link with the reporting channel.

Annotated fictional example: contact, time, origin and policy

Training reading at the fictional instant 22 October 2026, 10:00 UTC. The two Contact occurrences are ordered; the two languages have equal priority. Expiry is six months later. This is not Cyber Intelligence Embassy’s security.txt file and provides no real reporting channel.

# Fictional training example, not this site's reporting policy
Contact: mailto:security@publisher.example
Contact: https://publisher.example/report
Expires: 2027-04-22T10:00:00Z
Canonical: https://publisher.example/.well-known/security.txt
Policy: https://publisher.example/disclosure-policy
Preferred-Languages: fr, en

This example remains unsigned. Canonical identifies the expected URI but does not replace authenticity evidence. Before sending a sensitive report, verify the recipient, policy and appropriate transmission protections.

Eight situations separating format, freshness and trust

Each excerpt isolates one question; no conclusion is a complete file validation. Observations and proposed next steps are editorial guidance. Addresses shown in excerpts are not links to contact.

Essential fields are present

Fictional retrieval URI : https://publisher.example/.well-known/security.txt

Contact: mailto:security@publisher.example
Expires: 2027-04-22T10:00:00Z
Canonical: https://publisher.example/.well-known/security.txt

A contact, future expiry and the expected canonical URI appear in this excerpt.

Continue checking transport, recipient identity and policy. These fields prove neither mailbox operation nor testing permission.

Contact contains a bare email address
Contact: security@publisher.example
Expires: 2027-04-22T10:00:00Z

The mailto: scheme is missing; the value lacks the URI form required for Contact.

Correct the source publication. A tool’s possible tolerance does not establish format conformity.

Expires occurs twice
Contact: mailto:security@publisher.example
Expires: 2027-01-22T10:00:00Z
Expires: 2027-04-22T10:00:00Z

Two occurrences conflict with the Expires uniqueness rule.

Publish one expiry after correcting the file. Silently choosing the more convenient date conceals the publication defect.

The expiry date has passed
Contact: mailto:security@publisher.example
Expires: 2026-10-21T10:00:00Z

At the fictional evaluation instant the file expired twenty-four hours earlier.

Treat its data as stale and seek a verified current channel. Retain the old copy as history without presenting it as a current contact.

Canonical omits the retrieval URI

Fictional retrieval URI : https://api.publisher.example/.well-known/security.txt

Contact: mailto:security@publisher.example
Expires: 2027-04-22T10:00:00Z
Canonical: https://publisher.example/.well-known/security.txt

The file retrieved for api.publisher.example lists only publisher.example in Canonical.

Apply the recommendation not to trust these contents in this context and request publication verification. Similar hostnames do not resolve the mismatch.

The report concerns a subdomain

Fictional retrieval URI : https://publisher.example/.well-known/security.txt

Host concerned by the report : https://api.publisher.example/

Contact: mailto:security@publisher.example
Expires: 2027-04-22T10:00:00Z

The file belongs to publisher.example; the reported asset is api.publisher.example.

Do not infer subdomain coverage. Check its own discovery location and the product scope explicitly described in the policy.

The file redirects to a provider

Fictional redirect chain : https://publisher.example/.well-known/security.txt → https://intake.partner.example/security.txt

Contact: https://intake.partner.example/report
Expires: 2027-04-22T10:00:00Z

The redirect chain changes host and ends at intake.partner.example.

Document each hop and verify the channel delegation. Using a provider proves neither fraud nor authenticity.

An encryption key is referenced, but not authenticated
Contact: mailto:security@publisher.example
Expires: 2027-04-22T10:00:00Z
Encryption: https://publisher.example/report-key.asc

Encryption supplies an HTTPS key URI without local evidence of the key’s identity.

Authenticate the key through an appropriate means before use. Separate report encryption, file signing and actual protection of the submitted message.

From discovered channel to disclosure case: six useful records

The CERT/CC guide distinguishes finding a contact, providing a useful report and coordinating disclosure. The following outline is a local working proposal, imposing neither a universal fix deadline nor automatic publication.

From discovered channel to disclosure case: six useful records
RecordHow it helpsLimit to state
Product and versionConnect the report to a team and affected releases.A website and an embedded component may have different owners.
Observed behaviourExplain expected and actual results with appropriate reproduction steps.Separate reproduced facts, impact hypotheses and untested conditions.
Channel and recipientsKeep the discovery URL, chosen contact and consulted policy.Send sensitive evidence only after verifying the recipient and transmission protection.
Owner and follow-upRecord acknowledgement, case identifier and agreed next contact.Acknowledgement confirms neither impact nor remediation.
Affected partiesIdentify maintainers, suppliers and products sharing the component.A supplier’s fix does not establish deployment by every consumer.
Fix and communicationConnect fixed versions, remaining limits and actions expected from users.Record the agreed timetable and revisit it as facts change; Expires does not dictate a public disclosure date.

Three limits to keep visible

  • The presence or absence of security.txt alone neither grants nor denies testing permission; applicable conditions need separate verification.
  • RFC 9116 recommends an OpenPGP signature for the file; verifying a signature and establishing trust in its key remain distinct questions.
  • A compromised site can publish a false contact. Intrusions or suspected file tampering may call for an independent channel; this mechanism primarily addresses vulnerability response.

Primary sources and scope

Sources checked on

官方参考文献

参考文献支持该方法。 请根据您的实际情况调整检查;它们并非认证。 原始参考文献标题和源文档可能使用其他语言。

参考资料查阅日期 .