返回提示词目录第 1150 页

协调开源项目安全修复发布

为漏洞修复安排私下协作、披露时间、下游通知与版本发布,并准备公告和报告者沟通稿。

完整提示词

<context>
Small projects handle their first real vulnerability under pressure and often leak it: the fix is pushed to a public branch with a revealing commit message, a public issue is opened to "track" it, or CI logs show the test. Coordinated disclosure means fixing in private (a private security fork or patch shared by mail), agreeing a disclosure date with the reporter, getting an identifier (forges that act as CVE numbering authorities can issue one from a draft advisory; otherwise another CNA can), giving distributions and big downstream users a short heads-up under embargo if the issue is serious, then releasing the fix, the advisory and the identifier together. Patch releases for every supported line should ship at the same time, and the advisory should say clearly who is affected and what to do, without a working exploit.
</context>

<task>
Plan the coordinated release of a fix.

<report>
{{report}}
</report>

<project>
{{project}}
</project>

1. Severity and scope: affected versions and configurations, who is realistically exposed, and a severity rating with the reasoning (CVSS vector if the maintainers want one, marked as their decision). Flag anything you need confirmed.
2. Timeline: a dated plan back from a proposed disclosure date, respecting the reporter's deadline and the project's published policy if one exists. Typical pieces: fix ready, review, identifier requested, downstream notice, release. Say what happens if the issue becomes public early or is seen being exploited: release as soon as a fix exists.
3. Private fix: where to develop it privately, who reviews, how to keep CI and commit messages from revealing it, tests to add, and backports to each supported line.
4. Identifier and advisory: how to request a CVE id through the forge's advisory feature or another CNA, the fields needed, and when the advisory goes public.
5. Downstream notice: whether a pre-notice is warranted, who gets it (distribution security teams, large dependents, maintainers of forks), what to share and the embargo terms. Keep the group small.
6. Release day checklist: publish packages to every registry, push the tags and fix commits, publish the advisory, update the changelog, notify the reporter and the downstream list, post a short announcement.
7. Draft the advisory text: summary, affected and fixed versions, impact, workarounds, credit, references.
8. Draft two messages to the reporter: acknowledging and proposing the timeline, and the release-day thanks with credit as they wish to be named.
</task>

<constraints>
- Do not write or include exploit code or step-by-step exploitation in the advisory or any message.
- Do not invent versions, dates, registries or the reporter's name; use placeholders where missing.
- Do not suggest silently fixing without an advisory, or pressuring the reporter to stay quiet indefinitely.
- If the project has no published security policy, add writing one as a follow-up, not a blocker.
{{> output/uncertainty}}
</constraints>

<output_format>
## Severity and scope
Bullets.

## Timeline
Table: Date | Step | Owner.

## Private fix
Numbered steps.

## Identifier and advisory
Bullets.

## Downstream notice
Bullets, or "Not needed" with the reason.

## Release day
Checklist.

## Advisory draft
The advisory text in a fenced block.

## Reporter messages
Two short drafts.
</output_format>

可替换内容

  • {{report}}
  • {{project}}
  • {{> output/uncertainty}}

分类与标签

编程开发、漏洞修复、协调披露、开源维护

前往 AI 图片创作