TGViewer
Channel Public Channel
Hackerone Reports

Hackerone Reports

@hackeronereports

Last Check 2026-10-17 23:45:01
Subscribers
243
Photos
0
Videos
0
Links
788

Showing posts older than #680 · Back to latest

Older Posts 20 shown
Post #678 36
🎯 New Report #3650582: Missing access control when linking trackers to campaigns
🔺Severity: Medium
👽 Reporter: darky os
⭐️ Reputation: 1118
🛠 State: resolved
💼 Team: Revive Adserver
💵 Bounty: null
🕐 Submitted: 2026-04-05
⏰ Disclosed: 2026-06-03 13:35:00
📝 Summary: A missing access control check was reported when linking trackers to campaigns through the "campaign-trackers.php" script of Revive Adserver 6.0.6 and earlier. A low-privileged user could link their trackers to campaigns owned by other managers on the same instance, resulting in inconsistent ownership relationships. Ownership validation has been added to ensure that campaigns can only be linked to trackers owned by the same advertiser.
📂 Report JSON File: 3650582
@hackeronereports
Post #677 40
🎯 New Report #3650504: Missing access control when linking banners or campaigns to zones
🔺Severity: Medium
👽 Reporter: darky os
⭐️ Reputation: 1118
🛠 State: resolved
💼 Team: Revive Adserver
💵 Bounty: null
🕐 Submitted: 2026-04-05
⏰ Disclosed: 2026-06-03 13:35:20
📝 Summary: A missing access control check was identified when linking banners or campaigns to a zone through the zone-include.php script of Revive Adserver 6.0.6 and earlier, or via its API. This could have allowed a low-privileged user to link their zones to banners or campaigns owned by other managers on the same instance, resulting in inconsistent ownership relationships. Ownership validation has been added to ensure that banners and campaigns can only be linked to zones managed by the same account.
📂 Report JSON File: 3650504
@hackeronereports
Post #672 40
🎯 New Report #3355766: DLL side-loading vulnerability in Sony Music Center for PC Ver. 2.7.2 (Latest version)
🔺Severity: High
👽 Reporter: resurrect20
⭐️ Reputation: 121
🛠 State: resolved
💼 Team: Sony
💵 Bounty: null
🕐 Submitted: 2025-09-23
⏰ Disclosed: 2026-06-05 09:10:24
📝 Summary: A DLL side-loading vulnerability was discovered in Sony Music Center for PC Ver. 2.7.2. The application insecurely searched for a missing DLL file in the system PATH environment, allowing an attacker with access to the victim's local machine to achieve arbitrary code execution by placing a malicious DLL file in the PATH. The vulnerability was referenced in the MITRE ATT
Post #671 41
🎯 New Report #3625210: PIN bypass in PassCodeActivity via back button
🔺Severity: Medium
👽 Reporter: alper ozturk
⭐️ Reputation: 107
🛠 State: resolved
💼 Team: Nextcloud
💵 Bounty: null
🕐 Submitted: 2026-03-24
⏰ Disclosed: 2026-06-07 08:14:49
📝 Summary: A vulnerability was discovered in the PassCodeActivity of a certain application. The vulnerability allowed bypassing the PIN code by pressing the back button.
📂 Report JSON File: 3625210
@hackeronereports
Post #670 47
🎯 New Report #3489490: Authentication Bypass in ID4me handling via Missing JWT Signature Verification in User OIDC
🔺Severity: High
👽 Reporter: priyanka010
⭐️ Reputation: 131
🛠 State: resolved
💼 Team: Nextcloud
💵 Bounty: 2500
🕐 Submitted: 2026-01-07
⏰ Disclosed: 2026-06-07 09:16:00
📝 Summary: An authentication bypass vulnerability was discovered in the ID4me handling in the OIDC implementation. The vulnerability was caused by missing JWT signature verification for user authentication.
📂 Report JSON File: 3489490
@hackeronereports
Post #666 326
🎯 New Report #2701701: Injection in path parameter of Ingress-nginx
🔺Severity: High
👽 Reporter: fisjkars
⭐️ Reputation: 334
🛠 State: resolved
💼 Team: Kubernetes
💵 Bounty: null
🕐 Submitted: 2024-09-05
⏰ Disclosed: 2026-03-07 05:10:30
📝 Summary: A vulnerability was discovered in the Ingress-nginx controller where an attacker could inject arbitrary content into the path parameter of an Ingress. This allowed the attacker to upload a malicious nginx configuration file to the ingress controller's file system and then include that file in a subsequent Ingress. The attacker could then execute arbitrary code on the ingress controller.
📂 Report JSON File: 2701701
@hackeronereports
Post #665 287
🎯 New Report #1734639: IDOR to make someone attend or leave an event
🔺Severity: Medium
👽 Reporter: safehacker 2715
⭐️ Reputation: 3063
🛠 State: resolved
💼 Team: LinkedIn
💵 Bounty: null
🕐 Submitted: 2022-10-13
⏰ Disclosed: 2026-03-06 02:55:04
📝 Summary: An Insecure Direct Object Reference (IDOR) vulnerability was discovered in LinkedIn's event attendance functionality. The vulnerability allowed an attacker to manipulate event attendance by modifying the fsd profile parameter in POST requests to the voyagerScheduledcontentDashViewerStates API endpoint. This issue has been fixed.
📂 Report JSON File: 1734639
@hackeronereports
Post #664 226
🎯 New Report #2339192: Blocking a company page admin prevents him from delete paid media admin or edit his roles
🔺Severity: Medium
👽 Reporter: riadalrashed
⭐️ Reputation: 604
🛠 State: resolved
💼 Team: LinkedIn
💵 Bounty: null
🕐 Submitted: 2024-01-29
⏰ Disclosed: 2026-03-05 23:37:30
📝 Summary: A company page admin was prevented from managing (deleting or editing roles of) a paid media admin when the paid media admin blocked the company page admin. This created an access control vulnerability where administrative privileges were circumvented through the platform's social blocking feature.
📂 Report JSON File: 2339192
@hackeronereports
Post #663 191
🎯 New Report #3581815: Open Redirect on lovable.dev via redirect parameter leads to phishing attacks
🔺Severity: null
👽 Reporter: jdc94
⭐️ Reputation: 123
🛠 State: resolved
💼 Team: Lovable VDP
💵 Bounty: null
🕐 Submitted: 2026-03-02
⏰ Disclosed: 2026-03-05 22:38:35
📝 Summary: An open redirect vulnerability was discovered on the website lovable.dev. After logging in, a request was sent to a URL with a 'redirect' parameter. By supplying a backslash-prefixed value for the 'redirect' parameter, the user could be redirected to an external domain. This vulnerability could have been exploited to craft malicious URLs on the lovable.dev domain that redirect users to arbitrary external sites.
📂 Report JSON File: 3581815
@hackeronereports
Post #662 163
🎯 New Report #3524779: DoS via Unbounded Memory Allocation in sendWebStream on Fastify v5.7.0 leads to OOM crash when backpressure is ignored
🔺Severity: null
👽 Reporter: onlybugs05
⭐️ Reputation: 140
🛠 State: resolved
💼 Team: Fastify
💵 Bounty: null
🕐 Submitted: 2026-01-26
⏰ Disclosed: 2026-03-05 15:49:48
📝 Summary: A vulnerability was discovered in Fastify versions 5.7.0 and later. The issue was in the "sendWebStream" function, which failed to handle TCP backpressure correctly. When a ReadableStream was sent as a response, Fastify continuously pulled data from the stream producer and wrote it to the response object, ignoring the return value of the write operation. This allowed a fast producer to fill the server's memory indefinitely, leading to an Out-Of-Memory (OOM) crash if a client stopped reading the response.
📂 Report JSON File: 3524779
@hackeronereports
Post #661 126
🎯 New Report #3506183: Missing Access Control in MigrationFile allows attacker to upload files to any Migration
🔺Severity: High
👽 Reporter: ahacker1
⭐️ Reputation: 6459
🛠 State: resolved
💼 Team: GitHub
💵 Bounty: null
🕐 Submitted: 2026-01-10
⏰ Disclosed: 2026-03-05 02:23:08
📝 Summary: A Missing Authorization vulnerability was identified in GitHub Enterprise Server that allowed unauthorized content to be uploaded to a user's repository migration export due to a missing authorization check in the repository migration upload endpoint. The vulnerability could be exploited by supplying the migration identifier to overwrite or replace a victim's migration archive.
📂 Report JSON File: 3506183
@hackeronereports
Post #660 122
🎯 New Report #3580247: Use after free in hyperfifo example
🔺Severity: None
👽 Reporter: deepbluev7
⭐️ Reputation: 100
🛠 State: informative
💼 Team: curl
💵 Bounty: null
🕐 Submitted: 2026-03-02
⏰ Disclosed: 2026-03-03 06:54:27
📝 Summary: null
📂 Report JSON File: 3580247
@hackeronereports
Post #659 125
🎯 New Report #3356149: 2FA requirement bypass when inviting team members
🔺Severity: Medium
👽 Reporter: 0x7ashish
⭐️ Reputation: 117
🛠 State: resolved
💼 Team: Omise
💵 Bounty: null
🕐 Submitted: 2025-09-24
⏰ Disclosed: 2026-02-28 20:55:04
📝 Summary: The application's requirement for users to enable 2FA before sending team invitations was bypassed by modifying client-side responses. This allowed invitations to be sent without enabling 2FA, defeating the security requirement.
📂 Report JSON File: 3356149
@hackeronereports
Older posts →
Threads Profile ViewerView any public Threads profile without an account.Open ThreadLook →Writing with AI? Make it sound human.Metric37 rewrites AI drafts so they read naturally. Free AI detector, 1,500 words free.Try Metric37 →