<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>OSV-Scanner on AmeyArc</title><link>https://amey-thakur.github.io/tags/osv-scanner/</link><description>Recent content in OSV-Scanner on AmeyArc</description><generator>Hugo -- 0.152.2</generator><language>en-us</language><lastBuildDate>Wed, 02 Sep 2026 22:41:48 -0400</lastBuildDate><atom:link href="https://amey-thakur.github.io/tags/osv-scanner/index.xml" rel="self" type="application/rss+xml"/><item><title>A Stack-Overflow Denial of Service in Google's OSV-Scanner</title><link>https://amey-thakur.github.io/posts/2026-09-02-a-stack-overflow-denial-of-service-in-googles-osv-scanner/</link><pubDate>Wed, 02 Sep 2026 22:41:48 -0400</pubDate><guid>https://amey-thakur.github.io/posts/2026-09-02-a-stack-overflow-denial-of-service-in-googles-osv-scanner/</guid><description>OSV-Scanner reads the licence text of every package it scans, and it parsed that text with a recursive descent that had no depth limit. Roughly three megabytes of open brackets exhausted the goroutine stack. In Go a stack overflow is a fatal error rather than a panic, so recover cannot catch it and one malformed package ended the entire scan. This is the report, the forty lines that fixed it, and what contributing upstream to Google actually involved.</description></item></channel></rss>