CVE-2022-46265
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 · uneditedA vulnerability has been identified in Polarion ALM (All versions < V2304.0). The affected application contains a Host header injection vulnerability that could allow an attacker to spoof a Host header information and redirect users to malicious websites.
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 confidencePolarion ALM versions prior to V2304.0 contain a Host header injection vulnerability where the application does not properly validate or sanitize the Host header in incoming HTTP requests. An attacker can manipulate the Host header to cause the application to generate links or redirects pointing to attacker-controlled domains, potentially leading to phishing attacks against users.
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< 2304.0CVSS 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
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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.
-
Confirm Polarion ALM is installedLocate the Polarion installation directory or check for the Polarion web application running on your server (typically port 443 or 8080)Affected if Polarion ALM software is present and running in your environment
-
Identify the installed Polarion ALM versionAccess the Polarion web interface and look for version information in the application (usually found in the Help > About section, or check the installation logs or configuration files)Affected if You cannot determine the version or find it listed in the application
-
Compare your version against the affected rangeCheck if the installed version is below V2304.0 (any version prior to 2304.0, including older major versions)Affected if The installed version is less than 2304.0
-
Verify the web interface is accessibleConfirm the Polarion ALM web application is currently running and accessible via HTTP/HTTPSAffected if The application is accessible over the network and accepts HTTP requests
-
Test Host header handling (optional validation)Send a crafted HTTP request with a modified Host header (for example, Host: attacker.com) and observe if the application reflects this value in generated links, redirects, or emailsAffected if The application reflects the manipulated Host header in any response or generated content
You are affected if Polarion ALM is installed and running with a version lower than V2304.0, and the web interface is accessible to process incoming HTTP requests with manipulated Host headers.
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.
dbcve · scoped2304.0
Upgrade Polarion ALM to version V2304.0 or later, which contains the fix for this vulnerability. Alternatively, configure the application server to validate and reject unexpected Host header values.
V2304.0 (Polarion ALM version 2304.0)
- 1. Back up the current Polarion ALM installation, configuration files, and database before starting the upgrade process
- 2. Download Polarion ALM version 2304.0 or later from the official Siemens/Cert portal or your authorized distribution channel
- 3. Stop the Polarion ALM service to ensure a clean upgrade
- 4. Install the upgrade following the standard Polarion ALM installation procedure for version 2304.0
- 5. After installation, start the Polarion ALM service
- 6. Verify the application is running correctly and confirm the Host header injection vulnerability is resolved by testing that arbitrary Host headers are no longer accepted or reflected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46265 — 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-46265 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