LiveActive security incident?Get immediate response
CVE Record

CVE-2022-43515: X-Forwarded-For header is active by default causes access to Zabbix sites in maintenance mode

Zabbix Frontend provides a feature that allows admins to maintain the installation and ensure that only certain IP addresses can access it. In this way, any user will not be able to access the Zabbix Frontend while it is being maintained and possible sensitive data will be prevented from being disclosed. An attacker can bypass this protection and access the instance using IP address not listed in the defined range.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Zabbix Frontend maintenance mode can be bypassed because X-Forwarded-For handling is active by default. A non-allowed user may access the frontend during maintenance, undermining a control meant to limit visibility while work is underway.

Executive priority

Treat this as a moderate-priority remediation for Zabbix environments. It is not described as data theft or full compromise, but it weakens maintenance isolation and may expose administrative surfaces when operators expect access to be restricted.

Technical view

CVE-2022-43515 affects Zabbix Frontend versions listed by the CVE bundle. The issue is improper input handling around client IP determination, allowing maintenance-mode access controls to be bypassed via X-Forwarded-For behavior. CVSS 3.1 is 5.3 with network access, no authentication, and low complexity.

Likely exposure

Exposure is most relevant for internet- or network-accessible Zabbix Frontend deployments using maintenance mode IP restrictions, especially behind proxies or load balancers where forwarded client headers are present.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation evidence. The flaw is remotely reachable and unauthenticated, but the documented impact is limited to bypassing maintenance-mode access restrictions.

Researcher notes

The source bundle maps this to CWE-20 and CVSS vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N. Evidence supports a maintenance-mode authorization bypass, not broader Zabbix server compromise. Fixed-version details should be confirmed from Zabbix or distribution advisories.

Mitigation direction

  • Inventory Zabbix Frontend versions against the listed affected ranges.
  • Apply Zabbix or distribution security updates addressing CVE-2022-43515.
  • Review reverse proxy and trusted header handling for Zabbix Frontend.
  • Restrict frontend access at the network layer during maintenance windows.
  • Monitor Zabbix frontend logs for unexpected access during maintenance mode.

Validation and detection

  • Confirm installed Zabbix Frontend versions are outside affected ranges.
  • Check Debian or vendor package changelogs for this CVE.
  • Verify maintenance mode blocks non-allowlisted clients in a controlled test.
  • Review proxy configuration for unsafe forwarded-header trust.
  • Confirm compensating network controls cover the frontend during maintenance.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-43515 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2022-43515Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ZabbixFrontend4.0.0-4.0.44, 5.0.0-5.0.29, 6.0.0-6.0.9, 6.2.0-6.2.4, 5.0.30rc1, 6.0.11rc1, 6.2.5rc1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.