dbcve.org
Solution ManagerApplication · Sap

CVE-2022-41275

MEDIUM · 6.1 CVSS v3.1 Published 2022-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
In SAP Solution Manager (Enterprise Search) - versions 740, and 750, an unauthenticated attacker can generate a link that, if clicked by a logged-in user, can be redirected to a malicious page that could read or modify sensitive information, or expose the user to a phishing attack, with little impact on confidentiality and integrity.

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 confidence

This is an open redirect vulnerability in SAP Solution Manager's Enterprise Search functionality. An unauthenticated attacker can craft malicious URLs containing a redirect parameter that, when clicked by a logged-in user, redirects the victim to an external malicious website. This enables phishing attacks and potential information disclosure through the user's established session.

MitigationImplement strict URL validation and whitelist-based redirect logic for the Enterprise Search functionality. All redirect targets should be validated against an allowlist of trusted domains before performing the redirect.

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
Solution ManagerApplication
Affected:= 740= 750

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SAP Solution Manager version
    Log into SAP Solution Manager and navigate to System Overview or use transaction SM51 to check the installed release version. Alternatively, check the SAP Note or system information in the SAP Manager.
    Affected if The installed version is 740 or 750.
  2. Verify Enterprise Search is enabled
    Access the SAP Solution Manager configuration for Enterprise Search (transaction SE16 or via the Fiori launchpad if available). Check if the Enterprise Search component is active and configured.
    Affected if Enterprise Search functionality is enabled and accessible to users.
  3. Test for vulnerable redirect parameter
    Locate the Enterprise Search URL endpoint. Common paths include /sap/bc/rest/search or similar REST endpoints. Inspect the URL for redirect-related parameters such as 'redirect', 'url', 'target', or 'link'. Attempt to append a test parameter with an external domain (e.g., redirect=http://example.com) and observe if the application performs an uncontrolled redirect.
    Affected if The application accepts and follows redirects to arbitrary external domains without validation.
  4. Check URL validation configuration
    Review SAP Solution Manager security configuration files and web dispatcher settings for redirect validation rules. Look for any whitelist or allowlist configurations related to URL redirects.
    Affected if No strict URL validation or allowlist-based redirect logic is configured.

Your environment is affected if you run SAP Solution Manager versions 740 or 750 with Enterprise Search enabled, and the system performs unrestricted redirects to external URLs based on user-supplied parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict URL validation and whitelist-based redirect logic for the Enterprise Search functionality. All redirect targets should be validated against an allowlist of trusted domains before performing the redirect.

Fix this in Solution Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41275 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41275 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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