For one, we now have a vulnerability disclosure policy (VDP) that covers vulns discovered in our own stuff and in other parties’ assets.
Secondly, it means that we’ll occasionally publish artisanal, bespoke CVE entries (CVEs) for these vulnerabilities. For more on AHA!’s CVE assignment scope, see our CVE Numbering Authority page on MITRE’s site.
Our VDP is derived from the disclose.io Policymaker, edited to cover vulnerability reports involving other parties.
AHA! welcomes feedback from security researchers and the general public to help improve our security and the security of the internet in general. Click the below to read more about that.
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.
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.
Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.
When working with us, according to this policy, you can expect us to:
In participating in our vulnerability disclosure program in good faith, we ask that you:
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.
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.
For issues involving other parties, please see additional requirements, below. Note, these requirements do not apply to AHA! assets.
When we publish CVEs, we will tend to use this template, adjusted to taste.
|CVE-2023-0666||0x00c7||Wireshark RTPS Parsing Buffer Overflow|
|CVE-2023-0667||0x00c7||Wireshark MSMMS parsing buffer overflow|
|CVE-2023-0668||0x00c7||Wireshark IEEE-C37.118 parsing buffer overflow|
|CVE-2023-2905||0x00c8||Cesanta Mongoose MQTT Message Parsing Heap Overflow|
|CVE-2023-2906||0x00c8||Wireshark CP2179 divide by zero|
|CVE-2023-4504||0x00c9||CUPS/libppd PostScript Parsing Heap Overflow|
We’ve reserved the following CVEs for upcoming publication.
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 must be either (1) presented at a regular AHA! meeting, (2) disclosed directly to the affected party, or (3) kept to yourself.