diff --git a/skills/.curated/vuln-report-writing/LICENSE.txt b/skills/.curated/vuln-report-writing/LICENSE.txt new file mode 100644 index 0000000..7a4a3ea --- /dev/null +++ b/skills/.curated/vuln-report-writing/LICENSE.txt @@ -0,0 +1,202 @@ + + Apache License + Version 2.0, January 2004 + http://www.apache.org/licenses/ + + TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION + + 1. Definitions. + + "License" shall mean the terms and conditions for use, reproduction, + and distribution as defined by Sections 1 through 9 of this document. + + "Licensor" shall mean the copyright owner or entity authorized by + the copyright owner that is granting the License. + + "Legal Entity" shall mean the union of the acting entity and all + other entities that control, are controlled by, or are under common + control with that entity. For the purposes of this definition, + "control" means (i) the power, direct or indirect, to cause the + direction or management of such entity, whether by contract or + otherwise, or (ii) ownership of fifty percent (50%) or more of the + outstanding shares, or (iii) beneficial ownership of such entity. + + "You" (or "Your") shall mean an individual or Legal Entity + exercising permissions granted by this License. + + "Source" form shall mean the preferred form for making modifications, + including but not limited to software source code, documentation + source, and configuration files. + + "Object" form shall mean any form resulting from mechanical + transformation or translation of a Source form, including but + not limited to compiled object code, generated documentation, + and conversions to other media types. + + "Work" shall mean the work of authorship, whether in Source or + Object form, made available under the License, as indicated by a + copyright notice that is included in or attached to the work + (an example is provided in the Appendix below). + + "Derivative Works" shall mean any work, whether in Source or Object + form, that is based on (or derived from) the Work and for which the + editorial revisions, annotations, elaborations, or other modifications + represent, as a whole, an original work of authorship. For the purposes + of this License, Derivative Works shall not include works that remain + separable from, or merely link (or bind by name) to the interfaces of, + the Work and Derivative Works thereof. + + "Contribution" shall mean any work of authorship, including + the original version of the Work and any modifications or additions + to that Work or Derivative Works thereof, that is intentionally + submitted to Licensor for inclusion in the Work by the copyright owner + or by an individual or Legal Entity authorized to submit on behalf of + the copyright owner. For the purposes of this definition, "submitted" + means any form of electronic, verbal, or written communication sent + to the Licensor or its representatives, including but not limited to + communication on electronic mailing lists, source code control systems, + and issue tracking systems that are managed by, or on behalf of, the + Licensor for the purpose of discussing and improving the Work, but + excluding communication that is conspicuously marked or otherwise + designated in writing by the copyright owner as "Not a Contribution." + + "Contributor" shall mean Licensor and any individual or Legal Entity + on behalf of whom a Contribution has been received by Licensor and + subsequently incorporated within the Work. + + 2. Grant of Copyright License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + copyright license to reproduce, prepare Derivative Works of, + publicly display, publicly perform, sublicense, and distribute the + Work and such Derivative Works in Source or Object form. + + 3. Grant of Patent License. Subject to the terms and conditions of + this License, each Contributor hereby grants to You a perpetual, + worldwide, non-exclusive, no-charge, royalty-free, irrevocable + (except as stated in this section) patent license to make, have made, + use, offer to sell, sell, import, and otherwise transfer the Work, + where such license applies only to those patent claims licensable + by such Contributor that are necessarily infringed by their + Contribution(s) alone or by combination of their Contribution(s) + with the Work to which such Contribution(s) was submitted. If You + institute patent litigation against any entity (including a + cross-claim or counterclaim in a lawsuit) alleging that the Work + or a Contribution incorporated within the Work constitutes direct + or contributory patent infringement, then any patent licenses + granted to You under this License for that Work shall terminate + as of the date such litigation is filed. + + 4. Redistribution. You may reproduce and distribute copies of the + Work or Derivative Works thereof in any medium, with or without + modifications, and in Source or Object form, provided that You + meet the following conditions: + + (a) You must give any other recipients of the Work or + Derivative Works a copy of this License; and + + (b) You must cause any modified files to carry prominent notices + stating that You changed the files; and + + (c) You must retain, in the Source form of any Derivative Works + that You distribute, all copyright, patent, trademark, and + attribution notices from the Source form of the Work, + excluding those notices that do not pertain to any part of + the Derivative Works; and + + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file, excluding those notices that do not + pertain to any part of the Derivative Works, in at least one + of the following places: within a NOTICE text file distributed + as part of the Derivative Works; within the Source form or + documentation, if provided along with the Derivative Works; or, + within a display generated by the Derivative Works, if and + wherever such third-party notices normally appear. The contents + of the NOTICE file are for informational purposes only and + do not modify the License. You may add Your own attribution + notices within Derivative Works that You distribute, alongside + or as an addendum to the NOTICE text from the Work, provided + that such additional attribution notices cannot be construed + as modifying the License. + + You may add Your own copyright statement to Your modifications and + may provide additional or different license terms and conditions + for use, reproduction, or distribution of Your modifications, or + for any such Derivative Works as a whole, provided Your use, + reproduction, and distribution of the Work otherwise complies with + the conditions stated in this License. + + 5. Submission of Contributions. Unless You explicitly state otherwise, + any Contribution intentionally submitted for inclusion in the Work + by You to the Licensor shall be under the terms and conditions of + this License, without any additional terms or conditions. + Notwithstanding the above, nothing herein shall supersede or modify + the terms of any separate license agreement you may have executed + with Licensor regarding such Contributions. + + 6. Trademarks. This License does not grant permission to use the trade + names, trademarks, service marks, or product names of the Licensor, + except as required for reasonable and customary use in describing the + origin of the Work and reproducing the content of the NOTICE file. + + 7. Disclaimer of Warranty. Unless required by applicable law or + agreed to in writing, Licensor provides the Work (and each + Contributor provides its Contributions) on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or + implied, including, without limitation, any warranties or conditions + of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A + PARTICULAR PURPOSE. You are solely responsible for determining the + appropriateness of using or redistributing the Work and assume any + risks associated with Your exercise of permissions under this License. + + 8. Limitation of Liability. In no event and under no legal theory, + whether in tort (including negligence), contract, or otherwise, + unless required by applicable law (such as deliberate and grossly + negligent acts) or agreed to in writing, shall any Contributor be + liable to You for damages, including any direct, indirect, special, + incidental, or consequential damages of any character arising as a + result of this License or out of the use or inability to use the + Work (including but not limited to damages for loss of goodwill, + work stoppage, computer failure or malfunction, or any and all + other commercial damages or losses), even if such Contributor + has been advised of the possibility of such damages. + + 9. Accepting Warranty or Additional Liability. While redistributing + the Work or Derivative Works thereof, You may choose to offer, + and charge a fee for, acceptance of support, warranty, indemnity, + or other liability obligations and/or rights consistent with this + License. However, in accepting such obligations, You may act only + on Your own behalf and on Your sole responsibility, not on behalf + of any other Contributor, and only if You agree to indemnify, + defend, and hold each Contributor harmless for any liability + incurred by, or claims asserted against, such Contributor by reason + of your accepting any such warranty or additional liability. + + END OF TERMS AND CONDITIONS + + APPENDIX: How to apply the Apache License to your work. + + To apply the Apache License to your work, attach the following + boilerplate notice, with the fields enclosed by brackets "[]" + replaced with your own identifying information. (Don't include + the brackets!) The text should be enclosed in the appropriate + comment syntax for the file format. We also recommend that a + file or class name and description of purpose be included on the + same "printed page" as the copyright notice for easier + identification within third-party archives. + + Copyright [yyyy] [name of copyright owner] + + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. \ No newline at end of file diff --git a/skills/.curated/vuln-report-writing/SKILL.md b/skills/.curated/vuln-report-writing/SKILL.md new file mode 100644 index 0000000..25e0f89 --- /dev/null +++ b/skills/.curated/vuln-report-writing/SKILL.md @@ -0,0 +1,51 @@ +--- +name: vuln-report-writing +description: Create professional offensive-security report content for bug bounty findings or full penetration-test reports. Use when asked to write a vulnerability finding (asset, description, impact, remediation, references, PoC steps) or to assemble a pentest report with executive summary, scope, methodology, findings, and recommendations. +--- + +# Vuln Report Writing + +## Overview +Create clear, reproducible, no-hype vulnerability reports for bug bounty submissions or pentest deliverables using strict, triage-friendly structure. + +## Workflow Decision Tree +1. Identify mode: **Bug bounty finding** or **Pentest report**. +2. Collect inputs: asset, vuln type, affected components, evidence/PoC, impact, remediation, references. +3. Draft using the required structure; keep language factual and concise. +4. Validate for clarity and reproducibility; add assumptions if data is missing. + +## Mode A: Bug Bounty Finding +Use the exact fields and order below: +1. Affected asset +2. Description (2–3 sentences) +3. Impact (1–2 sentences) +4. Remediation (1–2 sentences) +5. References (prefer OWASP; otherwise high-quality vendor/standards) +6. Evidence/PoC (1–4 short steps; mention Burp where appropriate) + +Template: see `references/bugbounty-finding.md`. + +## Mode B: Pentest Report +Include standard report sections plus findings in the Mode A format. +Required sections: +- Executive summary (short, non-technical) +- Scope (in-scope assets only) +- Methodology (high level, non-sensitive) +- Findings (each in Mode A format) +- Risk overview (aggregate themes, not hype) +- Recommendations (prioritized, pragmatic) +- Appendix (optional: tooling list, test accounts, evidence index) + +Template: see `references/pentest-report.md`. + +## Quality Rules (apply to both modes) +- Keep claims factual; avoid exaggeration or speculative impact. +- Make reproduction easy; write steps as short, testable actions. +- State assumptions when required inputs are missing. +- Show impact clearly and directly; avoid buzzwords. +- Prefer OWASP references; otherwise use vendor/standards docs. + +## Resources +- `references/bugbounty-finding.md` for the finding template and phrasing guidance. +- `references/pentest-report.md` for the full report structure. +- `references/owasp-refs.md` for commonly used OWASP references. diff --git a/skills/.curated/vuln-report-writing/references/bugbounty-finding.md b/skills/.curated/vuln-report-writing/references/bugbounty-finding.md new file mode 100644 index 0000000..093e87e --- /dev/null +++ b/skills/.curated/vuln-report-writing/references/bugbounty-finding.md @@ -0,0 +1,29 @@ +# Bug Bounty Finding Template + +Use this exact order and keep each field concise. + +Affected asset: +- [hostname or endpoint, environment] + +Description (2-3 sentences): +- [What is vulnerable, where, and how it can be triggered] + +Impact (1-2 sentences): +- [Direct security outcome and business effect; no speculation] + +Remediation (1-2 sentences): +- [Specific fix or control, minimal and actionable] + +References: +- [Prefer OWASP reference from owasp-refs.md; otherwise vendor/standards] + +Evidence/PoC (1-4 short steps): +1) [Step 1] +2) [Step 2] +3) [Step 3] +4) [Step 4] + +Notes: +- Mention Burp explicitly when used (e.g., "Intercept with Burp" or "Replay in Burp Repeater"). +- Use exact endpoints, parameters, and example IDs where safe. +- If a detail is unknown, mark it as [assumption] and state it once. diff --git a/skills/.curated/vuln-report-writing/references/owasp-refs.md b/skills/.curated/vuln-report-writing/references/owasp-refs.md new file mode 100644 index 0000000..a715252 --- /dev/null +++ b/skills/.curated/vuln-report-writing/references/owasp-refs.md @@ -0,0 +1,27 @@ +# OWASP References (Common) + +Use these when mapping findings to a high-quality reference. + +OWASP Top 10 (2021) overview: +- https://owasp.org/Top10/ + +Category pages: +- A01: Broken Access Control: https://owasp.org/Top10/A01_2021-Broken_Access_Control/ +- A02: Cryptographic Failures: https://owasp.org/Top10/A02_2021-Cryptographic_Failures/ +- A03: Injection: https://owasp.org/Top10/A03_2021-Injection/ +- A04: Insecure Design: https://owasp.org/Top10/A04_2021-Insecure_Design/ +- A05: Security Misconfiguration: https://owasp.org/Top10/A05_2021-Security_Misconfiguration/ +- A06: Vulnerable and Outdated Components: https://owasp.org/Top10/A06_2021-Vulnerable_and_Outdated_Components/ +- A07: Identification and Authentication Failures: https://owasp.org/Top10/A07_2021-Identification_and_Authentication_Failures/ +- A08: Software and Data Integrity Failures: https://owasp.org/Top10/A08_2021-Software_and_Data_Integrity_Failures/ +- A09: Security Logging and Monitoring Failures: https://owasp.org/Top10/A09_2021-Security_Logging_and_Monitoring_Failures/ +- A10: Server-Side Request Forgery (SSRF): https://owasp.org/Top10/A10_2021-Server-Side_Request_Forgery_%28SSRF%29/ + +OWASP Cheat Sheet Series: +- https://cheatsheetseries.owasp.org/ + +OWASP ASVS: +- https://owasp.org/www-project-application-security-verification-standard/ + +Fallback guidance: +- If no OWASP mapping fits, use a vendor or standards reference (e.g., RFC, W3C, cloud provider docs). diff --git a/skills/.curated/vuln-report-writing/references/pentest-report.md b/skills/.curated/vuln-report-writing/references/pentest-report.md new file mode 100644 index 0000000..ca6ba9f --- /dev/null +++ b/skills/.curated/vuln-report-writing/references/pentest-report.md @@ -0,0 +1,31 @@ +# Pentest Report Template (Concise) + +Title: +- [Client/Engagement Name] +- Date: [YYYY-MM-DD] + +Executive summary (short, non-technical): +- [2-5 sentences: overall posture, main risks, business impact] + +Scope: +- In scope: [assets, environments] +- Out of scope: [assets, constraints] +- Assumptions: [if any] + +Methodology (high level): +- [Black/gray/white-box], [auth/no-auth], [time window], [tools if needed] + +Findings: +- Use the Bug Bounty Finding Template for each finding. +- Order by severity or exploitability. + +Risk overview: +- [Common themes, systemic issues, recurring controls] + +Recommendations: +- [Prioritized actions, grouped by theme] + +Appendix (optional): +- Test accounts +- Evidence index +- Tooling list