CVE-2022-34914
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 · uneditedWebswing before 22.1.3 allows X-Forwarded-For header injection. The client IP address is associated with a variable in the configuration page. The {clientIp} variable can be used as an application startup argument. The X-Forwarded-For header can be manipulated by a client to store an arbitrary value that is used to replace the clientIp variable (without sanitization). A client can thus inject multiple arguments into the session startup. Systems that do not use the clientIP variable in the configuration are not vulnerable. The vulnerability is fixed in these versions: 20.1.16, 20.2.19, 21.1.8, 21.2.12, and 22.1.3.
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 confidenceWebswing before 22.1.3 is vulnerable to X-Forwarded-For header injection. The application uses the X-Forwarded-For header value to populate the {clientIp} variable, which can be used as an application startup argument. Since this value is not sanitized before insertion, an attacker can manipulate the X-Forwarded-For header to inject arbitrary arguments into the session startup process, potentially leading to remote code execution.
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< 20.1.16>= 20.2, < 20.2.19>= 21.1.0, < 21.1.8>= 21.2.0, < 21.2.12>= 22.1.0, < 22.1.3CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify Webswing versionCheck the Webswing server version (typically visible in the admin console or startup logs) and compare it against the affected ranges: < 20.1.16, 20.2.x to < 20.2.19, 21.1.x to < 21.1.8, 21.2.x to < 21.2.12, or 22.1.x to < 22.1.3Affected if The installed version falls within any of these ranges
-
Locate application startup configurationFind the Webswing configuration file or admin interface where application startup arguments are defined (commonly in the security or startup settings)Affected if A configuration exists for startup arguments
-
Check for {clientIp} variable usageInspect the startup argument configuration for the presence of the literal string {clientIp} which gets replaced with the X-Forwarded-For header value at runtimeAffected if The {clientIp} variable is present in the startup arguments
-
Verify X-Forwarded-For handlingReview the Webswing configuration or proxy setup to confirm that X-Forwarded-For headers from incoming requests are being processed and passed through to the applicationAffected if X-Forwarded-For header handling is enabled and the {clientIp} variable is used in startup arguments
You are affected if your Webswing version is in the vulnerable range AND the {clientIp} variable is used in your application startup arguments while X-Forwarded-For headers are being processed.
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 · scoped20.1.1620.2.1921.1.8
Upgrade Webswing to version 22.1.3 or later (or 20.1.16/20.2.19/21.1.8/21.2.12 for LTS branches). If immediate upgrade is not possible, audit configurations to ensure {clientIp} variable is not used in application startup arguments.
22.1.3 (or the latest 22.x release; alternatively the version-specific fix for your branch: 20.1.16, 20.2.19, 21.1.8, or 21.2.12)
- 1. Identify your current Webswing version from the administration console or server logs
- 2. Determine which version branch you are currently on (20.1.x, 20.2.x, 21.1.x, 21.2.x)
- 3. Download the appropriate fixed version for your branch: 20.1.16, 20.2.19, 21.1.8, 21.2.12, or preferably 22.1.3
- 4. Review the Webswing upgrade documentation at www.webswing.org for version-specific migration steps
- 5. Back up your current Webswing configuration, including the webswing.config file and any custom applications
- 6. Stop the Webswing server gracefully
- 7. Install the new version following the standard installation process
- 8. Restore your backed-up configuration files to the new installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34914 — 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-34914 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