Fortiauthenticator Agent For Microsoft Outlook Web AccessApplication · Fortinet
CVE-2022-22304
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn improper neutralization of input during web page generation vulnerability [CWE-79] in FortiAuthenticator OWA Agent for Microsoft version 2.2 and 2.1 may allow an unauthenticated attacker to perform an XSS attack via crafted HTTP GET requests.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a stored XSS vulnerability in FortiAuthenticator OWA Agent for Microsoft versions 2.1 and 2.2 where improper input validation allows unauthenticated attackers to inject malicious JavaScript payloads via crafted HTTP GET requests. The injected script executes when legitimate users access the compromised OWA agent pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Fortiauthenticator Agent For Microsoft Outlook Web AccessApplication
= 2.1= 2.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify FortiAuthenticator OWA Agent installationLocate and confirm the presence of FortiAuthenticator Agent For Microsoft Outlook Web Access on the system or FortiAuthenticator applianceAffected if The product is not found or only the OWA Agent component is not installed, then not affected
-
Identify installed OWA Agent versionUse the system's software inventory, package manager, or FortiAuthenticator admin interface to retrieve the exact version number of the FortiAuthenticator OWA AgentAffected if Installed version matches 2.1 or 2.2 exactly, indicating the vulnerable versions
-
Confirm OWA Agent is enabledCheck the FortiAuthenticator configuration or admin interface to verify whether the Outlook Web Access Agent module is actively enabled and accessibleAffected if OWA Agent is enabled and reachable, making the XSS exploitable through HTTP GET requests
-
Inspect OWA Agent configuration for injected scriptsExamine OWA Agent configuration files, web templates, or user input fields for unexpected script tags, JavaScript declarations, or encoded payloadsAffected if Script tags or malicious JavaScript code are found stored in OWA Agent configuration or web pages
-
Review logs for suspicious GET requestsAnalyze FortiAuthenticator and OWA Agent access logs for HTTP GET requests containing script tags, javascript: URIs, or other XSS patterns targeting the OWA Agent endpointsAffected if Log entries show unauthenticated GET requests with XSS payloads targeting OWA Agent URLs
You are affected if FortiAuthenticator OWA Agent version 2.1 or 2.2 is installed and the OWA Agent component is enabled and accessible to users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade FortiAuthenticator OWA Agent to version 2.3 or later which contains the patched input validation. As an interim control, implement web application firewall rules to sanitize or block suspicious GET request patterns containing script tags.
Fix this in Fortiauthenticator Agent For Microsoft Outlook Web Access
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22304 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-22304 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data