sonares vs Sonar

sonares präsentiert ScienceFacts auf der Science Week

Das Berliner Startup sonares präsentiert seine ScienceFacts auf der Science Week in Berlin. Zudem wird Prof. Oliver Günther, Präsident der Universität Potsdam, Vorsitzender des wissenschaftlichen Beirats von sonares.

Wissenschaft gegen Fake News: Uni-Präsident führt sonares-Beirat an

Mit Prof. Oliver Günther gewinnt das Berliner Startup einen hoch renommierten Wissenschaftler als Vorsitzenden seines wissenschaftlichen Beirats.

Sonar DNS Field Command Injection Fixed by Developer

A developer discovered a command injection vulnerability in the DNS custom resolver field of Sonar, a macOS network scanning tool. The field, which accepts user input for custom DNS servers like Pi-hole or NextDNS, was passed to a privileged command without proper validation, potentially allowing arbitrary code execution as root. The fix involved allowlisting input to only accept valid IP addresses, passing arguments as an array instead of a shell string, and narrowing the privileged interface. The article also details three other security fixes made during a full pass: moving API tokens from a plist to the Keychain, preventing CSV export formula injection, and implementing atomic writes to avoid data corruption.

• Sonar had a command injection vulnerability in its DNS resolver field.
• The vulnerability could allow running commands as root.
• The fix involves allowlisting IP addresses and using array arguments.

Validators Should Judge, Not Auto-Remediate

Todd Linnertz argues that AI validators in developer toolchains should only judge outputs and not perform automatic remediation. He introduces and adopts the term "verification debt" to describe the quality gap between machine-produced outputs and production-ready software, and highlights testing patterns like inner-loop vs outer-loop checks and shadow testing. Linnertz criticizes validator designs (citing Sonar's "Solve" stage) that collapse finding and fixing into one step because they erase audit trails, change the security posture, and hide authorship of changes. He recommends separating the validator (which emits a verdict) from a remediation agent (which proposes fixes) and enforcing a frozen baseline promotion gate so fixes must clear the same checks as any other change. He notes the industry has not yet settled where remediation should live.

• Author Todd Linnertz advocates that validators should judge only and not perform remediation.
• The article adopts the term "verification debt" to describe the gap between AI-produced outputs and production-quality requirements.
• Sonar's framework is described as having a "Solve" stage where the validator both finds issues and fixes them.