dbcve.org
Layer7 Api Management Oauth ToolkitApplication · Broadcom

CVE-2021-30650

MEDIUM · 6.1 CVSS v3.1 Published 2022-02-18
Fix available
A fix is available. Upgrade to 4.4.1 or later.
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
A reflected cross-site scripting (XSS) vulnerability in the Symantec Layer7 API Management OAuth Toolkit (OTK) allows a remote attacker to craft a malicious URL for the OTK web UI and target OTK users with phishing attacks or other social engineering techniques. A successful attack allows injecting malicious code into the OTK web UI client application.

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

A reflected cross-site scripting (XSS) vulnerability in the Symantec Layer7 API Management OAuth Toolkit (OTK) web UI allows remote attackers to inject malicious script through specially crafted URLs, which are then executed in the context of targeted OTK users' sessions.

MitigationApply vendor-supplied patches or updates for the OAuth Toolkit. Until patched, user education on avoiding clicking untrusted links can help reduce phishing risk.

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
Layer7 Api Management Oauth ToolkitApplication
Affected:< 4.4.1

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 if OAuth Toolkit web UI is installed
    Locate the OTK installation directory, typically under the Layer7 API Gateway installation path (e.g., /opt/SecureSpan/Gateway/runtime/modules/otk or C:\Program Files\Layer7\API Gateway\runtime\modules\otk). Check for the presence of the 'otk' folder containing OAuth-related components.
    Affected if The OTK web UI component directory exists on the system
  2. Determine OAuth Toolkit version
    Check the version file or manifest within the OTK installation directory. Common locations include a version.properties, MANIFEST.MF, or the OTK installer filename. Alternatively, access the OTK login page and check any version information displayed in the UI footer.
    Affected if The installed version is lower than 4.4.1 (e.g., 4.4.0, 4.3.x, earlier versions)
  3. Verify web UI is accessible
    Confirm the OTK web interface is reachable by accessing the OAuth Toolkit endpoint, typically at /otk/ or /oauth/ relative to the Gateway hostname. Use a browser or curl to test connectivity.
    Affected if The OTK web UI is exposed and accessible over the network
  4. Check if OTK is enabled
    Review the Layer7 API Gateway configuration to confirm the OAuth Toolkit extension is loaded and active. Check gateway configuration files or the Policy Manager for OTK-related policies.
    Affected if The OTK module is enabled and loaded in the Gateway configuration

The environment is affected if the Broadcom Layer7 API Management OAuth Toolkit is installed with a version lower than 4.4.1 and the OTK web UI is enabled and accessible.

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.

dbcve · scoped
Upgrade available Upgrade to 4.4.1 or later
Fixed in 4.4.1
Interim mitigation

Apply vendor-supplied patches or updates for the OAuth Toolkit. Until patched, user education on avoiding clicking untrusted links can help reduce phishing risk.

Recommended fix Moderate confidence

4.4.1 or later

  1. Backup the current Layer7 API Management OAuth Toolkit installation and configuration
  2. Download OAuth Toolkit version 4.4.1 or later from the Broadcom support portal (support.broadcom.com)
  3. Stop the Layer7 API Gateway services
  4. Install the OTK 4.4.1 or later upgrade following the standard upgrade procedures
  5. Restart the Layer7 API Gateway services
  6. Verify the OTK installation and functionality
Caveat Review OTK 4.4.1 release notes for any configuration or compatibility changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Layer7 Api Management Oauth Toolkit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-30650 — 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-2021-30650 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