AHA Logo

Austin Hackers Anonymous

About Us Chat CVE Mailing List Meetings Our Spawn Rules


CVE

Until this sentence is removed, please consider this entire page in progress and therefore, should not be relied upon as accurate or useful information.

Anonymous Hacking Alliance is pursuing an effort to become a research oriented CVE Numbering Authority, under the MITRE program root.

To that end, AHA! will be adopting a vulnerability disclosure policy (VDP) for issues that we become aware of during meetings. We’ll also be maintaining a collection of artisanal, bespoke CVE entries (CVEs) that we publish.

Our VDP is derived from the disclose.io Policymaker, edited to cover vulnerability reports involving other parties.

Vulnerability Disclosure Policy

AHA! welcomes feedback from security researchers and the general public to help improve our security and the security of the internet in general.

If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any of our assets, we want to hear from you. This would include, but is not limited to, the AHA! website, AHA! e-mail services, and other AHA! communication channels.

If you believe you have discovered a security issue involving another party, we are happy to help you report that issue to the appropriate organizataion. Please see “Systems in Scope,” below.

This policy outlines steps for reporting vulnerabilities to us, what we expect, what you can expect from us.

Systems in Scope

This policy applies to any digital assets owned, operated, or maintained by AHA!

Because AHA! is a research organization, we will also accept vulnerability reports involving assets owned, operated, or maintained by another organization which is not already participating as a CVE Numbering Authority.

Out of Scope

Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.

Our Commitments

When working with us, according to this policy, you can expect us to:

Our Expectations

In participating in our vulnerability disclosure program in good faith, we ask that you:

Official Channels

Please report security issues affecting AHA! via [email protected], providing all relevant information. The more details you provide, the easier it will be for us to triage and fix the issue.

Please report security issues affecting other parties during one of our regularly scheduled meetings if you wish for AHA! to coordinate vulnerability disclosure (including generating a CVE ID) for you. We will not accept vulnerability reports involving other parties that are not presented at a AHA! meeting.

Safe Harbor

When conducting vulnerability research, according to this policy, we consider this research conducted under this policy to be:

You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our Official Channels before going any further.

Note that the Safe Harbor applies only to legal claims under the control of the organization participating in this policy, and that the policy does not bind independent third parties.

Generating AHA! CVEs

For issues involving other parties, please see additional requirements, below. Note, these requirements do not apply to AHA! assets.

Contact

Any questions about the AHA! CVE program should be directed to [email protected].

Vulnerabilities involving AHA! should be reported to [email protected].

Vulnerabilities involving other parties should be either presented at a regular AHA! meeting, the affected vendor, or kept to yourself.

Published CVEs

We haven’t issued any CVEs yet.

Reserved CVEs

We haven’t reserved any CVE IDs yet.

Fork me on GitHub