Day 4 of 1460 minExploit ArchitectHands-on lab

Day 4: Exposed Vector Databases and Weak Authentication

Taught by Mr Elite Updated

By the end of today you can

  • Start a local vector store with no authentication and enumerate every collection and raw payload with curl
  • Probe for open admin and snapshot routes and record what an unauthenticated caller can do
  • Enable an API key, then test whether it is enforced on every route and whether read-only keys exist
  • Use the GraphQL introspection lab to practise the same discovery habit against an API that describes itself

A team ships a RAG assistant. The app has a login, roles, and a tidy permissions model. Behind it sits a vector database, started from the quick-start Docker command, listening on a port that the cloud firewall happens to allow. Nobody set a key because the app talks to it from inside the network, and that felt safe enough.

Today you test that exact situation, on your own machine. The vector store holds the raw text of every chunk, the metadata, and often the source filenames. If the API answers without a key, the application's authorization never comes into play. You skip the front door and read the shelves.

In this lesson

  • Why the vector store is its own target
  • Watch me do it: an open store, then a locked one
  • Now lock it and compare
  • Key scope, rotation and what to record
  • Lab: discovery against a self-describing API

Premium course

$27 one-time, lifetime access

This day is part of the full course. Unlock it to read every lesson, do every mission and track your progress to the end.

Privileged members get every paid course included. See the plans