Froxlor has a BIND Zone File Injection via Unsanitized DNS Record Content in DomainZones::add()
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| froxlor | froxlor | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Froxlor | Froxlor |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-47hf-23pw-3m8c | Froxlor has a BIND Zone File Injection via Unsanitized DNS Record Content in DomainZones::add() |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.347% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Froxlor
Froxlor froxlor |
|
| CPEs | cpe:2.3:a:froxlor:froxlor:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Froxlor
Froxlor froxlor |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Froxlor is open source server administration software. Prior to version 2.3.6, `DomainZones::add()` accepts arbitrary DNS record types without a whitelist and does not sanitize newline characters in the `content` field. When a DNS type not covered by the if/elseif validation chain is submitted (e.g., `NAPTR`, `PTR`, `HINFO`), content validation is entirely bypassed. Embedded newline characters in the content survive `trim()` processing, are stored in the database, and are written directly into BIND zone files via `DnsEntry::__toString()`. An authenticated customer can inject arbitrary DNS records and BIND directives (`$INCLUDE`, `$ORIGIN`, `$GENERATE`) into their domain's zone file. Version 2.3.6 fixes the issue. | |
| Title | Froxlor has a BIND Zone File Injection via Unsanitized DNS Record Content in DomainZones::add() | |
| Weaknesses | CWE-93 | |
| References |
| |
| Metrics |
cvssV3_1
|