GHSA-JRWC-G36X-GQC7

Vulnerability from github – Published: 2026-08-07 12:31 – Updated: 2026-08-07 12:31
VLAI
Details

The Webbox of TeamDavid by Tobit Laboratories AG constructs redirect URLs using user-supplied input, which is appended to the redirect target in a 302 HTTP response. By using URL-encoded characters such as “%2e” (representing a dot), an attacker can manipulate the portion of the URL following the top-level domain (TLD). If a similar, registerable TLD exists (for example, if “.com” is the application’s domain, and “.company” is available for registration), an attacker can craft a URL to redirect users to a malicious “.company” domain. By using URL-encoded line feeds, it becomes possible to insert arbitrary response headers in the server's HTTP response.

This issue affects TeamDavid through Rollout 524.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-12071"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-601"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-07T10:16:56Z",
    "severity": "MODERATE"
  },
  "details": "The Webbox of TeamDavid by\u00a0Tobit Laboratories AG\u00a0constructs redirect URLs using user-supplied input, \nwhich is appended to the redirect target in a 302 HTTP response. By \nusing URL-encoded characters such as \u201c%2e\u201d (representing a dot), an \nattacker can manipulate the portion of the URL following the top-level \ndomain (TLD). If a similar, registerable TLD exists (for example, if \n\u201c.com\u201d is the application\u2019s domain, and \u201c.company\u201d is available for \nregistration), an attacker can craft a URL to redirect users to a \nmalicious \u201c.company\u201d domain. By using URL-encoded line feeds, it becomes\n possible to insert arbitrary response headers in the server\u0027s HTTP \nresponse.\n\n\n\nThis issue affects TeamDavid through Rollout 524.",
  "id": "GHSA-jrwc-g36x-gqc7",
  "modified": "2026-08-07T12:31:57Z",
  "published": "2026-08-07T12:31:57Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-12071"
    },
    {
      "type": "WEB",
      "url": "https://david.tobit.software/releasenotes"
    },
    {
      "type": "WEB",
      "url": "https://labs.infoguard.ch/posts/22-cves-in-david-a-secure-m365-alternative"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
      "type": "CVSS_V4"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…