PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

LINE Security Bug Bounty Program Report 2019

hackerone.com | blog | #bug-bounty | #vulnerability-disclosure | #hackerone | #transparency | #annual-report | #line
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

LINE Security's 2019 bug bounty report: the program migrated to HackerOne as a private program in July, received 101 reports with 37 rewarded (over 36%), and the first valid report earned $5,000.
Published
Collected

Related coverage

blog · hackerone.com
Report Smarter, Not Harder: HackerOne's Case for Better CIRCIA Rules
This coverage gives security teams current context for monitoring, validation, and remediation.
blog · wiz.io
Increasing transparency in cloud security: Wiz is now a CVE Numbering Authority (CNA)
Wiz became a CVE Numbering Authority able to assign CVE IDs and disclose cloud vulnerabilities—the latest step after helping build the community cloud vulnerability database.
blog · hackerone.com
Measuring The Fix: How We Evaluate Frontier Models on Remediation Quality
HackerOne tested frontier models on security fix quality and found the judge mattered more than the model. See how CTEM remediation earns engineer trust.
blog · hackerone.com
Critical PHP Vulnerabilities: What Security Teams Need to Know
Learn about the critical PHP vulnerabilities, HackerOne’s response, and the rise in reports. Review patching guidance and coordinated disclosure practices.
blog · hackerone.com
Project Glasswing: What We Learned Running a Frontier Model on Our Own Codebase
HackerOne ran Anthropic's Mythos 5 model against its own production code; it surfaced a critical RCE spanning three safe-in-isolation commits, illustrating compositional risk that diff review misses.
blog · hackerone.com
CTEM for Enterprise: Scaling Continuous Exposure Management Across Complex Environments
This coverage gives security teams current context for monitoring, validation, and remediation.
Back