dbcve.org
Asset Management XApplication · Microfocus

CVE-2023-4964

MEDIUM · 6.1 CVSS v3.1 Published 2023-10-30
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
Potential open redirect vulnerability in opentext Service Management Automation X (SMAX) versions 2020.05, 2020.08, 2020.11, 2021.02, 2021.05, 2021.08, 2021.11, 2022.05, 2022.11 and opentext Asset Management X (AMX) versions 2021.08, 2021.11, 2022.05, 2022.11. The vulnerability could allow attackers to redirect a user 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 · moderate confidence

Open redirect vulnerability in OpenText SMAX and AMX allows attackers to craft malicious URLs that redirect users to external websites. This occurs due to insufficient validation of redirect parameters, enabling phishing and credential theft attacks.

MitigationApply vendor-provided patches for the affected SMAX and AMX versions (2020.05-2022.11 for SMAX; 2021.08-2022.11 for AMX) or implement strict URL validation to restrict redirect targets to whitelisted domains.

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
Asset Management XApplication
Affected:= 2021.08= 2021.11= 2022.05= 2022.11
Service Management Automation XApplication
Affected:= 2020.05= 2020.08= 2020.11= 2021.02= 2021.05= 2021.08= 2021.11= 2022.05= 2022.11

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 installed AMX or SMAX version
    Locate the product version information in the system administration console, About page, or installation directory metadata. For SMAX, check the /smax/about endpoint or installation metadata files. For AMX, check the /amx/about endpoint or installation metadata.
    Affected if The installed version matches any of: SMAX 2020.05, 2020.08, 2020.11, 2021.02, 2021.05, 2021.08, 2021.11, 2022.05, 2022.11 OR AMX 2021.08, 2021.11, 2022.05, 2022.11
  2. Confirm web interface is enabled
    Verify that the SMAX or AMX web interface is accessible and not disabled. Check the service status and web configuration settings.
    Affected if The web interface is enabled and reachable, providing the attack surface for the open redirect vulnerability
  3. Check for unauthenticated URL redirect parameters
    Review web server logs or proxy logs for incoming requests containing redirect parameters (such as redirect=, url=, next=, target=, or similar) pointing to external domains. Use grep or log analysis tools to identify patterns like 'Location: http' in redirect responses.
    Affected if Requests containing redirect parameters that allow arbitrary external URLs are being processed without domain validation
  4. Inspect redirect handler configuration
    Examine the web application configuration files and URL validation rules for the redirect handler module. Look for allowlist or validation logic that controls where redirects can point.
    Affected if The redirect handler lacks strict domain allowlist validation or permits arbitrary external URLs in redirect parameters

You are affected if your installed SMAX or AMX version matches one of the affected releases (2020.05-2022.11 for SMAX, 2021.08-2022.11 for AMX) and the web interface is accessible, allowing attackers to craft malicious redirect URLs.

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

Apply vendor-provided patches for the affected SMAX and AMX versions (2020.05-2022.11 for SMAX; 2021.08-2022.11 for AMX) or implement strict URL validation to restrict redirect targets to whitelisted domains.

Fix this in Asset Management X 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-2023-4964 — 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-2023-4964 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