Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-54203 – Unauthenticated Sensitive Information Disclosure (Heap Memory Leak) – Tobit TeamDav

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-54203 is an unauthenticated sensitive information disclosure vulnerability in the Webbox module of Tobit Laboratories AG’s TeamDavid. Uninitialized heap memory is returned in HTTP responses from the /.well-known/mta-sts. endpoint, exposing residual data — including user passwords — to a remote, unauthenticated attacker. It is rated Critical (CVSS 9.2).

Technical details

  • Root cause: The /.well-known/mta-sts. handler allocates a response buffer with malloc() without zeroing it. When the requested file does not exist, the handler skips the ReadFile() call but still processes and returns the uninitialized buffer contents.
  • Trigger conditions: Repeatedly requesting the endpoint (e.g. non-existent file extensions), which returns residual heap memory from prior requests in an HTTP 200 response.
  • Attack vector: Network; no authentication or user interaction required.
  • Impact: Disclosure of up to ~4 KB of residual heap memory per request, containing sensitive artifacts from previous requests such as configuration data and credentials/passwords.

Affected software

  • Tobit Laboratories AG TeamDavid (Webbox module) — all versions through Rollout 524.

Severity

  • CVSS v4.0 base score: 9.2 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade to a fixed TeamDavid release beyond Rollout 524; monitor the vendor release notes (https://david.tobit.software/releasenotes) for the remediating rollout and apply it.
  • If no patch: Restrict internet exposure of the Webbox service; block or filter external requests to the /.well-known/mta-sts. endpoint at a reverse proxy or WAF, and rotate credentials that may have been exposed via memory disclosure.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Named response header (Server): David-WebBox
  • Page title: David InfoCenter Web

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge