basicsecurity.net
Proof, not just disclosure.
Threats / Rejetto / CVE-2024-23692
CVE-2024-23692 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Rejetto HTTP File Server vulnerability

Rejetto HTTP File Server contains a template injection vulnerability allowing remote, unauthenticated command execution via specially crafted HTTP requests.

Verdict

Today item — known-exploited.

A remote attacker can exploit improper neutralization of template engine elements to execute arbitrary commands on vulnerable HTTP File Server instances without authentication. Active exploitation in the wild increases operational risk.

CISA KEV Yes · 2024-07-093EPSS 0.99485 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
336 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-07-09).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.99485 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Rejetto, HTTP File Server. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-1336 Template Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft an HTTP request containing template injection payloads targeting the server's template engine.
Business
Exposed HTTP File Server instances become entry points for unauthorized system access and command execution.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I send the malicious request to the vulnerable server without requiring credentials or authentication.
Business
The lack of authentication requirements means any internet-facing instance is immediately exploitable by threat actors.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute arbitrary system commands through the template injection, gaining control over the affected host.
Business
Attackers can establish persistence, exfiltrate data, deploy malware, or pivot to internal network resources.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 336 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by VulnCheck (CNA)
  • Named finder/reporter credit (CVE.org)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • Disclosure & credit2
    Catalogued by VulnCheckCNA
    Credited with finding itArseniy Sharoglazovfinder