π¨ The ultimate agentic social media scheduling tool π€
TypeScript nextjsopen-sourceopen-source-social-media-scheduling-toolosspostiz-cloudpostiz-hostedredisscheduling-toolsocial-media-scheduling-tooltypescript
feat(security-policy): update endpoints and include dispute policy
Enno Gelhaus48bf76afa45b
diff --git a/SECURITY.md b/SECURITY.mdindex 956fa371b..5fa4f4085 100644--- a/SECURITY.md+++ b/SECURITY.md@@ -34,7 +34,7 @@ We consider an issue a vulnerability when it is a weakness in an in-scope, suppo**Not a vulnerability:**- Reports with no demonstrable security impact, or theoretical issues with no working proof of concept.-- Misconfiguration or non-default changes on a self-hosted instance (exposed database, missing TLS, weak operator-set secrets, these fall outside [Scope](#scope)).+- Misconfiguration or non-default changes on a self-hosted instance (exposed database, missing TLS, weak operator-set secrets); these fall outside [Scope](#scope).- Third-party dependency issues, unless Postiz's own use of the dependency is independently exploitable. Updating a dependency is not itself a vulnerability.- Denial-of-service, brute-force, or resource-exhaustion attacks absent a missing common defense.- Issues requiring physical or local access to a machine the user already controls.@@ -42,18 +42,29 @@ We consider an issue a vulnerability when it is a weakness in an in-scope, suppo- Missing hardening (security headers, cookie flags) with no demonstrated exploitable impact.- Reports affecting only end-of-life or unsupported versions (see [Supported Versions](#supported-versions)).-## Reporting Security Vulnerabilities+## Contacting Us++All security correspondence goes through [GAdvisory](https://postiz.gadvisory.org/request), our security advisory platform. The form routes four types of request:++- **Report a vulnerability.** See [Reporting Security Vulnerabilities](#reporting-security-vulnerabilities).+- **Dispute a CVE or Advisory.** Challenge the validity of a record we published. Disputes and their resolution are public and permanent. Our CVE Record Dispute Policy is linked from this flow.+- **Suggest a change to a CVE or Advisory.** Corrections to an existing record (affected versions, CWE, references, credits) where the finding itself is not in question.+- **Other.** Scope questions and anything that does not fit the above.-If you discover a security vulnerability in the Postiz app, please report it through the [GitHub Security Advisory system](https://github.com/gitroomhq/postiz-app/security/advisories/new).+If you are unsure which project a request concerns, or it is not about a single project, choose the general option on the project picker.-When reporting a security vulnerability, please provide as much detail as possible, including:+Private vulnerability reporting on GitHub is disabled for our repositories. GitHub Security Advisories are a publishing mirror only.++## Reporting Security Vulnerabilities++If you discover a security vulnerability in the Postiz app, report it through [GAdvisory](https://postiz.gadvisory.org/request). Please provide as much detail as possible, including:- A clear description of the vulnerability- Proof of concept (PoC), where possible- Steps to reproduce the vulnerability- Any relevant code or configuration files-If the report has immediate urgency, please contact one (or more) of the maintainers via email:+If the report has immediate urgency, please also contact one (or more) of the maintainers via email:- @egelhaus ([E-Mail](mailto:[email protected]))@@ -67,25 +78,16 @@ Reports that include AI-assisted analysis are welcome provided they have been vaWe follow a coordinated (private) disclosure model and will not publicly disclose a vulnerability until a fix or mitigation is available, to prevent exploitation before a patch is released. We ask reporters to operate the same way:-- Report privately through the channels above and do not publicly disclose, share, or discuss the issue, including partial details or proof-of-concept, until we have released a fix and published the corresponding advisory.+- Report privately through the channels above and do not publicly disclose, share, or discuss the issue, including partial details or proof-of-concept, until we have released a fix and published the corresponding advisory.- Allow a reasonable remediation window per the timelines below, and coordinate the public disclosure date with us.-- Avoid harming users, degrading service, or accessing/modifying data that is not your own while researching or demonstrating the issue.+- Avoid harming users, degrading service, or accessing or modifying data that is not your own while researching or demonstrating the issue.- Validate any AI-assisted analysis before submitting (see [AI Reports](#ai-reports)).During the embargo we will not confirm, deny, or discuss specifics of an unpatched vulnerability publicly. Reporters who follow this process are credited in the published advisory and in the CVE Record's credits section, unless they request otherwise.-## Security Vulnerability Response Process--We take security vulnerabilities seriously and will respond promptly to reports of vulnerabilities. Our response process includes:--- Investigating the report and verifying the vulnerability.-- Developing a patch or fix for the vulnerability.-- Releasing the patch or fix as soon as possible.-- Notifying users of the vulnerability and the patch or fix.--## Response Timelines+## Response Process and Timelines-We aim to follow these timelines:+For every report we investigate and verify the issue, develop a fix or mitigation, release it as soon as possible, and notify users through a published advisory. We aim to follow these timelines:- **Initial Acknowledgment:** Within 72 hours of initial report.- **Completed Triage / Verification:** Within 7 days of initial acknowledgment.@@ -99,6 +101,6 @@ Postiz operates as a CVE Numbering Authority (CNA) for the products listed under- **Reservation:** We reserve a CVE ID once a report is confirmed as a genuine in-scope vulnerability. Reservation is internal; the ID is not published or otherwise exposed at this stage.- **Assignment to reporter:** We provide the reserved CVE ID to the reporter so it can be referenced during coordinated disclosure.-- **Publication:** The CVE Record is published to the CVE List together with the public security advisory and fixed release, never before a fix or mitigation is available. We aim to publish within 24 hours of the remediation release.+- **Publication:** The CVE Record is published to the CVE List together with the public advisory at [postiz.gadvisory.org/advisories](https://postiz.gadvisory.org/advisories) and the fixed release, never before a fix or mitigation is available. We aim to publish within 24 hours of the remediation release.-CVE IDs are assigned only to vulnerabilities affecting currently supported versions (see [Supported Versions](#supported-versions)).\ No newline at end of file+CVE IDs are assigned only to vulnerabilities affecting currently supported versions (see [Supported Versions](#supported-versions)).