<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Oracle-Database on CuraSec</title><link>https://curasec.metacog.co.kr/tags/oracle-database/</link><description>Recent content in Oracle-Database on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 06 Aug 2026 13:03:19 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/oracle-database/index.xml" rel="self" type="application/rss+xml"/><item><title>Attackers deploy khunt toolkit inside Oracle DB via SQL injection</title><link>https://curasec.metacog.co.kr/insights/2026-08-06-hackers-run-khunt-post-exploitation-toolkit-from-oracle-data/</link><pubDate>Thu, 06 Aug 2026 13:03:19 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-06-hackers-run-khunt-post-exploitation-toolkit-from-oracle-data/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Any Oracle database exposed to untrusted SQL input is a plausible target; audit applications for SQL injection entry points into your Oracle instances and review whether extended stored procedures or Java capabilities are enabled, as khunt leverages in-database execution to move laterally. No CVE or patch cited, so schedule rather than emergency response.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> Running a post-exploitation toolkit from inside the database process is a meaningful evasion technique — build or tune detections for anomalous outbound connections and unusual child-process spawning from Oracle DB processes, and review whether your EDR covers database server hosts adequately.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>