<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Exploit on CuraSec</title><link>https://curasec.metacog.co.kr/tags/exploit/</link><description>Recent content in Exploit on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 23 Jul 2026 12:47:45 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/exploit/index.xml" rel="self" type="application/rss+xml"/><item><title>SANS ISC: Rondo exploit tool observed targeting GeoServer</title><link>https://curasec.metacog.co.kr/insights/2026-07-23-rondo-meets-geoserver-wed-jul-22nd/</link><pubDate>Thu, 23 Jul 2026 12:47:45 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-23-rondo-meets-geoserver-wed-jul-22nd/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> The summary is too thin to extract actionable detail, and the diary notes this is not a new attack technique. If you run GeoServer, verify you are patched against prior critical RCEs (e.g. CVE-2024-36401) and review your exposure; no new enrichment signals here.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> A SANS ISC diary about attack traffic hitting GeoServer may contain honeypot-derived detection patterns, but the garbled summary yields no usable IOCs or TTPs — read the full diary entry to assess whether log signatures are worth tuning.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>