<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Default-Credentials on CuraSec</title><link>https://curasec.metacog.co.kr/tags/default-credentials/</link><description>Recent content in Default-Credentials on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 08 Sep 2026 15:04:44 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/default-credentials/index.xml" rel="self" type="application/rss+xml"/><item><title>220 million traveler records exposed via APIS default credentials</title><link>https://curasec.metacog.co.kr/insights/2026-09-08-220-million-traveler-records-exposed-in-vietnam-linked-apis/</link><pubDate>Tue, 08 Sep 2026 15:04:44 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-08-220-million-traveler-records-exposed-in-vietnam-linked-apis/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> The root cause — default credentials left on a cloud-exposed system — is a textbook misconfiguration. No specific software or CVE is named, so there is no patch to apply; use this as a prompt to audit your own cloud services for default or uncycled credentials.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> A breach of this scale — spanning nearly a decade of passport and travel data — illustrates third-party government data custody risk. No direct vendor relationship action is needed for most organizations, but it is useful context for board-level discussions on supply-chain and sovereign data exposure.&lt;/li>
&lt;/ul></description></item></channel></rss>