Report a security issue

Use this page to tell Biamp about a vulnerability in one of our products, or about a system you believe has been compromised. Reports are read by the Biamp Product Security Incident Response Team. You do not need an account, and you do not have to tell us who you are.

A vulnerability is a flaw that could be used against a system. A compromise means you believe a system has already been broken into or is behaving as though someone else is controlling it. If you are not sure which one you have, pick the closest and describe it below — we will sort it out.

What are you reporting?

Vulnerability in a Biamp product

Suspected compromise of a deployed system

Vulnerability in a third-party component Biamp ships

Other security concern

NOTE: A flaw in software Biamp did not write but includes in its products — an open-source library, embedded OS, or licensed component. Use this if you found the issue in a component, or if a published CVE affects a version Biamp is shipping. Tell us the component and version if you know it.

Is this vulnerability being actively exploited?

Yes, I have evidence

I don't know

What evidence do you have of exploitation?

One-line summary

Description

"Actively exploited" means you have seen the flaw used against a real system, or you have evidence that it has been — not that you have shown it could be. A working proof of concept on your own bench is not active exploitation. If you are unsure, choose I don't know; it is a real answer and we treat it differently from "no".

Reporter

You can report anonymously. We never reject a report because we do not know who sent it. But without an email address we cannot acknowledge your report, cannot ask you follow-up questions, and cannot tell you when it is fixed.

Name

Organization

Preferred contact method

Contact detail

Your PGP public key or fingerprint

Preferred language

Credit preference

Classification and Disclosure

When did you discover this?

Is this already publicly known?

Yes

Not Sure

Public references

Have you reported this anywhere else?

Do you plan to disclose publicly?

No planned date

Yes

Date

Does this involve a third-party component?

Yes

Not sure

Which component, and which version?

Affected Product

Product family

Product name, as you know it

Model

Firmware or software version

Serial number

We ask because a report from a country we do not expect the product to be in is a signal worth chasing, and because it helps us judge how many customers are affected. Skip it if you would rather not say.

Where is the affected system deployed?

Not applicable / lab environment

Prefer not to say