CVE-2022-27671
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 CSRF token visible in the URL may possibly lead to information disclosure vulnerability.
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 · moderate confidenceThe application embeds CSRF tokens in URL parameters instead of using secure transmission methods like HTTP headers or POST body fields. This exposes tokens in server logs, browser history, proxy logs, and bookmarks, potentially allowing attackers to obtain valid CSRF tokens and perform cross-site request forgery attacks.
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= 420= 430CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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.
-
Identify SAP BusinessObjects BI Platform installationLocate the installation directory for SAP BusinessObjects, typically under /opt/sap_businessobjects or C:\Program Files\SAP BusinessObjects, and check for the bi platform subdirectoryAffected if The product is installed and is version 420 or 430
-
Verify installed version matches affected releasesCheck the version file or system information for the exact SAP BusinessObjects BI Platform version - look for version 420 or version 430 in installation metadata or the Central Management ConsoleAffected if Installed version is exactly 420 or exactly 430
-
Inspect application configuration for CSRF token methodReview the CSRF token configuration files in the BusinessObjects configuration directory, looking for settings that control token transmission method (query parameter vs header/body)Affected if CSRF tokens are configured to be passed via URL query parameters rather than HTTP headers or POST body
-
Examine server access logs for token exposureReview web server logs (Tomcat, Apache) in the BusinessObjects logs directory for URLs containing 'csrfToken' or similar parameter names in the query stringAffected if CSRF token values appear in server access logs or request history
A user is affected if they run SAP BusinessObjects BI Platform version 420 or 430 and have CSRF tokens transmitted via URL query parameters, with those tokens being logged or visible in browser history.
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 dataMigrate CSRF token handling from URL query parameters to hidden form fields or custom HTTP headers, and ensure tokens are validated server-side only when received via these secure methods.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27671 — 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-27671 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