Harman International Lifestyle Products & Services
By Harman Bug bounty on YesWeHack harman.com
- Top reward
- €4,000
- Top severity paid
- Critical
- Assets in scope
- 25
- Public CVEs
- 9
- Last change
At a glance
What to know before you start testing.
- Pays up to €4,000
- for critical bugs, from €100.
- Report on YesWeHack
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- No public write-ups
- Keep findings private.
Rewards
What YesWeHack lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical |
|
€4,000 |
| High |
|
€2,500 |
| Medium |
|
€1,000 |
| Low |
|
€300 |
- Safe harbor
-
Full
We will not pursue civil action or otherwise initiate a complaint or claim against you for circumventing the technological measures we have used to protect the applications in scope, so long as your activities are conducted in a manner consistent with these Program Terms.
Summarised with AI from the program policy on YesWeHack, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
25 assets you may test, 2 excluded.
APIs 7
- https://apis.onecloud.harman.com
- https://bluetooth-events.onecloud.harman.com
- https://edgeapis.onecloud.harman.com
- https://events.onecloud.harman.com
- https://ota.onecloud.harman.com
- https://quantum-events.onecloud.harman.com
- https://tms.onecloud.harman.com
Android apps 1
- https://play.google.com/store/apps/details?id=com.jbl.oneapp&hl=fr&gl=US
iOS apps 1
- https://apps.apple.com/fr/app/jbl-one/id1610239857
Products and areas 16
- Device: JBL Authentics 200
- Device: JBL Authentics 300
- Device: JBL Authentics 500
- Device: JBL Bar 1000MK2
- Device: JBL Bar 1300MK2
- Device: JBL Bar 300MK2
- Device: JBL Bar 500MK2
- Device: JBL Bar 700MK2
- Device: JBL Bar 800MK2
- Device: JBL Boombox 3 Wi-Fi
- Device: JBL Charge 5
- Device: JBL Charge 5 Wi-Fi
- Device: JBL Flip 7
- Device: JBL Live Beam 3
- Device: JBL PartyBox Encore 2
- Device: JBL Tour One M3
Out of scope (2)
- All domains or subdomains not listed in the above list of 'Scopes'
- Mobile app versions that are not currently in app stores.
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Harman International Lifestyle Products & Services (via YesWeHack)'s policy. "We" in these lines means the program, not this site.
While testing
-
Denial of service (DoS) attacks on Harman International applications, servers, networks or infrastructure are strictly forbidden.
-
Avoid tests that could cause degradation or interruption of our services.
-
Do not use automated scanners or tools that generate large amount of network traffic
-
Do not leak, copy, manipulate, or destroy any user data or files in any of our applications/servers.
-
No vulnerability disclosure, full, partial or otherwise, is allowed.
-
Make sure to apply hunting requirements policy (User-Agent, VPN...)
-
You must not be a former or current employee of Harman International or one of its contractors.
Not accepted
-
Broken Link/Social media Hijacking
-
Tabnabbing
-
Missing cookie flags
-
Content/Text injections
-
Clickjacking/UI redressing
-
Denial of Service (DoS) attacks
-
Recently disclosed CVEs (less than 30 days sinces patch release)
-
CVEs without exploitable vulnerabilities and PoC
-
Open ports or services without exploitable vulnerabilities and PoC
-
Social engineering of staff or contractors
-
Presence of autocomplete attribute on web forms
-
Vulnerabilities affecting outdated browsers or platforms
-
Self-XSS or XSS that cannot be used to impact other users
-
Any hypothetical flaw or best practices without exploitable vulnerabilities and PoC
-
SSL/TLS issues (e.g. expired certificates, best practices)
-
Unexploitable vulnerabilities (e.g. Self-XSS, XSS or Open Redirect through HTTP headers...)
-
Reports with attack scenarios requiring MITM or physical access to victim's device
-
Missing security-related HTTP headers which do not lead directly to an exploitable vulnerability and PoC
-
Low severity Cross-Site Request Forgery (CSRF) (e.g. Unauthenticated / Logout / Login / Products cart updates...)
-
Invalid or missing email security records (e.g. SPF, DKIM, DMARC)
-
Session management issues (e.g. lack of expiration, no logout on password change, concurrent sessions)
-
CSV injection
-
Malicious file upload (e.g. EICAR files, .EXE)
-
HTTP Strict Transport Security Header (HSTS)
Summarised with AI from the program policy on YesWeHack, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 8 minutes ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Scope added
Mobile app versions that are not currently in app stores. (out of scope)
-
Scope added
All domains or subdomains not listed in the above list of 'Scopes' (out of scope)
-
Scope added
https://bluetooth-events.onecloud.harman.com
-
Scope added
https://quantum-events.onecloud.harman.com
-
Scope added
https://tms.onecloud.harman.com
-
Scope added
https://play.google.com/store/apps/details?id=com.jbl.oneapp&hl=fr&gl=US
-
Scope added
https://apps.apple.com/fr/app/jbl-one/id1610239857
-
Scope added
Device: JBL Charge 5 Wi-Fi
-
Scope added
Device: JBL Boombox 3 Wi-Fi
-
Scope added
Device: JBL Authentics 500
-
Scope added
Device: JBL Authentics 300
-
Scope added
Device: JBL Authentics 200
-
Scope added
Device: JBL Bar 1300MK2
-
Scope added
Device: JBL Bar 1000MK2
-
Scope added
Device: JBL Bar 300MK2
-
Scope added
Device: JBL Charge 5
-
Scope added
Device: JBL Tour One M3
-
Scope added
Device: JBL Flip 7
-
Scope added
Device: JBL Live Beam 3
-
Scope added
Device: JBL PartyBox Encore 2
-
Scope added
https://edgeapis.onecloud.harman.com
-
Scope added
https://apis.onecloud.harman.com
-
Scope added
https://ota.onecloud.harman.com
-
Scope added
https://events.onecloud.harman.com
-
Scope added
Device: JBL Bar 800MK2
-
Scope added
Device: JBL Bar 700MK2
-
Scope added
Device: JBL Bar 500MK2
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
| CVE | Summary | Severity | Published |
|---|---|---|---|
| CVE-2019-19560 | An authentication bypass in the debug interface in Mercedes-Benz HERMES 1.5 allows an attacker with physical access to device hardware to obtain system information. | Medium 4.6 | 16 Nov 2020 |
| CVE-2019-19561 | A misconfiguration in the debug interface in Mercedes-Benz HERMES 1.5 allows an attacker with direct physical access to device hardware to obtain cellular modem information. | Low 2.4 | 16 Nov 2020 |
| CVE-2019-19562 | An authentication bypass in the debug interface in Mercedes-Benz HERMES 2.1 allows an attacker with physical access to device hardware to obtain system information. | Medium 4.6 | 16 Nov 2020 |
| CVE-2019-19563 | A misconfiguration in the debug interface in Mercedes-Benz HERMES 2.1 allows an attacker with direct physical access to device hardware to obtain cellular modem information. | Low 2.4 | 16 Nov 2020 |
| CVE-2019-19556 | An authentication bypass in the debug interface in Mercedes-Benz HERMES 1 allows an attacker with physical access to device hardware to obtain system information. | Medium 4.6 | 16 Nov 2020 |
| CVE-2019-19557 | A misconfiguration in the debug interface in Mercedes-Benz HERMES 1 allows an attacker with direct physical access to device hardware to obtain cellular modem information. | Low 2.4 | 16 Nov 2020 |
| CVE-2019-11224 | HARMAN AMX MVP5150 v2.87.13 devices allow remote OS Command Injection. | High 8.8 | 15 May 2019 |
| CVE-2016-1984 | The setUpSubtleUserAccount function in /bin/bw on Harman AMX devices before 2016-01-20 has a hardcoded password for the 1MB@tMaN account, which makes it easier for remote attackers to obtain access via a (1) SSH or (2) HTTP session, a different vulnerability than CVE-2015-8362. | Critical 9.8 | 22 Jan 2016 |
| CVE-2015-8362 | The setUpSubtleUserAccount function in /bin/bw on Harman AMX devices before 2015-10-12 has a hardcoded password for the BlackWidow account, which makes it easier for remote attackers to obtain access via a (1) SSH or (2) HTTP session, a different vulnerability than CVE-2016-1984. | Critical 9.8 | 22 Jan 2016 |
Original policy
Copied from yeswehack.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Rules
Harman International
Keeping user information safe and secure is a top priority and a core company value for us at Harman (“We”, “Us” or “Harman”).
We welcome the contribution of external security researchers and look forward to awarding them for their invaluable contribution to the security of all Harman customers.
In addition to the YesWeHack General Terms of Use for “Hunter” and any other applicable YesWeHack terms and conditions, these Bug Bounty Program Terms and Conditions (“Program Terms”) govern the participation of any Hunter (“You”, or “Hunter”) in the Harman Bug Bounty Program.
In the event of a conflict between these Program Terms and any other agreement or terms, these Program Terms shall control.
Program Rules
Testing Policy, Responsible Disclosure
Please adhere to the following rules while performing research on this program:
- Denial of service (DoS) attacks on Harman International applications, servers, networks or infrastructure are strictly forbidden.
- Avoid tests that could cause degradation or interruption of our services.
- Do not use automated scanners or tools that generate large amount of network traffic
- Do not leak, copy, manipulate, or destroy any user data or files in any of our applications/servers.
- No vulnerability disclosure, full, partial or otherwise, is allowed.
- Make sure to apply hunting requirements policy (User-Agent, VPN...)
####Note that safe harbor protections only apply to reports submitted via our bug bounty program####
Reward Eligibility
We are happy to thank everyone who submits valid reports which help us improve the security of Harman International, however only those that meet the following eligibility requirements may receive a monetary reward:
- You must be the first reporter of a vulnerability.
- The vulnerability must be a qualifying vulnerability
- The report must contain the following elements:
- Clear textual description of the vulnerability, how it can be exploited, the security impact it has on the application, its users and Harman International, and remediation advice on fixing the vulnerability
- Proof of exploitation: screenshots demonstrating the exploit was performed, and showing the final impact
- Provide complete steps with the necessary information to reproduce the exploit, including (if necessary) code snippets, payloads, commands etc
- You must not break any of the testing policy rules listed above
- You must not be a former or current employee of Harman International or one of its contractors.
Reward amounts are based on:
- Reward grid of the report's scope
- CVSS scoring and actual business impact of the vulnerability upon performing risk analysis
COMPLIANCE WITH THESE PROGRAM TERMS
We consider activities conducted in a manner consistent with these Program Terms to constitute “authorized” conduct under the United States Computer Fraud and Abuse Act, United States Digital Millennium Copyright Act, and any similar laws or regulations in other jurisdictions.
We will not pursue civil action or otherwise initiate a complaint or claim against you for circumventing the technological measures we have used to protect the applications in scope, so long as your activities are conducted in a manner consistent with these Program Terms.
We consider any activities conducted in a manner inconsistent with these Program Terms to be “unauthorized” conduct under the United States Computer Fraud and Abuse Act, and any similar laws or regulations in other jurisdictions. We reserve the right to take legal action against you for any such unauthorized conduct.
If your report addresses a vulnerability of a Harman business partner, Harman reserves the right to share your submission in its entirety, including your identity, with the business partner to help facilitate testing and resolution of the reported vulnerability. If legal action is initiated by a third party against you and you have complied with Harman’s Program Terms, Harman will take steps to make it known that your actions were conducted in compliance with these Program Terms.
If at any time you have concerns or are uncertain whether your security research is consistent with these Program Terms, or believe that these Program Terms do not address you security research, please inquire via www.yeswehack.com/contact/hunter-form before going any further.
GOVERNING LAW AND DISPUTE RESOLUTION
These Program Terms shall be subject to the internal laws of the State of New York, USA and are binding upon the parties hereto in the United States and worldwide. You and Harman agree that any claims between You and Harman, including claims against you for unauthorized conduct shall be subject shall be subject to the jurisdiction of courts in the city of New York City, New York.
THE FINE PRINT
You are responsible for paying any taxes associated with rewards. We may modify these Program Terms or terminate this program at any time. We won’t apply any changes we make to these Program Terms retroactively.
Out of scope
- All domains or subdomains not listed in the above list of 'Scopes'
- Mobile app versions that are not currently in app stores.
Qualifying vulnerabilities
- SQL Injection (SQLi)
- Cross-Site Scripting (XSS)
- Remote Code Execution (RCE)
- Insecure Direct Object Reference (IDOR)
- Horizontal and vertical privilege escalation
- Authentication bypass & broken authentication
- Business Logic Errors vulnerability with real security impact
- Local files access and manipulation (LFI, RFI, XXE, SSRF, XSPA)
- Cross-Origin Resource Sharing (CORS) with real security impact
- Cross-site Request Forgery (CSRF) with real security impact
- Open Redirect
- Bluetooth vulnerabilities
- Exposed secrets, credentials or sensitive information on an asset under our control and affecting at least one of our scopes
Non-qualifying vulnerabilities
- Broken Link/Social media Hijacking
- Tabnabbing
- Missing cookie flags
- Content/Text injections
- Clickjacking/UI redressing
- Denial of Service (DoS) attacks
- Recently disclosed CVEs (less than 30 days sinces patch release)
- CVEs without exploitable vulnerabilities and PoC
- Open ports or services without exploitable vulnerabilities and PoC
- Social engineering of staff or contractors
- Presence of autocomplete attribute on web forms
- Vulnerabilities affecting outdated browsers or platforms
- Self-XSS or XSS that cannot be used to impact other users
- Any hypothetical flaw or best practices without exploitable vulnerabilities and PoC
- SSL/TLS issues (e.g. expired certificates, best practices)
- Unexploitable vulnerabilities (e.g. Self-XSS, XSS or Open Redirect through HTTP headers...)
- Reports with attack scenarios requiring MITM or physical access to victim's device
- Missing security-related HTTP headers which do not lead directly to an exploitable vulnerability and PoC
- Low severity Cross-Site Request Forgery (CSRF) (e.g. Unauthenticated / Logout / Login / Products cart updates...)
- Invalid or missing email security records (e.g. SPF, DKIM, DMARC)
- Session management issues (e.g. lack of expiration, no logout on password change, concurrent sessions)
- Disclosure of information without exploitable vulnerabilities and PoC (e.g. stack traces, path disclosure, directory listings, software versions, IP disclosure, 3rd party secrets, EXIF Metadata, Origin IP)
- CSV injection
- Malicious file upload (e.g. EICAR files, .EXE)
- HTTP Strict Transport Security Header (HSTS)
- Subdomain takeover without a full exploitable vulnerability and PoC or not applicable to the scope
- Blind SSRF without exploitable vulnerabilities and PoC (e.g. DNS & HTTP pingback, Wordpress XMLRPC)
- Lack or bypass of rate-limiting, brute-forcing or captcha issues
- User enumeration (e.g. email, alias, GUID, phone number, common CMS endpoints)
- Weak password policies (e.g. length, complexity, reuse)
- Ability to spam users (email / SMS / direct messages flooding)
- Disclosed or misconfigured public API keys (e.g. Google Maps, Firebase, analytics tools...)
- Password reset token sent via HTTP referer to external services (e.g. analytics / ads platforms)
- Stolen secrets, credentials or information gathered from a third-party asset that we have no control over
- Exposed secrets, credentials or information on an asset under our control that are not applicable to the program’s scope
- Pre-account takeover (e.g. account creation via oAuth)
- GraphQL Introspection is enabled
- Outdated libraries without demonstrated exploitability
- Rooted/jailbroken device-only attacks
- Attacks that require root