CVE-2023-41699
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 · uneditedURL Redirection to Untrusted Site ('Open Redirect') vulnerability in Payara Platform Payara Server, Micro and Embedded (Servlet Implementation modules) allows Redirect Access to Libraries.This issue affects Payara Server, Micro and Embedded: from 5.0.0 before 5.57.0, from 4.1.2.191 before 4.1.2.191.46, from 6.0.0 before 6.8.0, from 6.2023.1 before 6.2023.11.
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 confidenceOpen Redirect vulnerability in Payara Platform's Servlet Implementation modules allows attackers to craft malicious URLs that redirect users to untrusted external sites. This occurs due to insufficient validation of redirect URLs, enabling phishing and credential theft 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>= 4.1.2.191, < 4.1.2.191.46>= 5.0.0, < 5.57.0>= 6.0.0, < 6.8.0>= 6.2023.1, < 6.2023.11CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Payara Platform versionRun 'asadmin version' from the Payara installation bin directory, or check the admin console (typically at https://localhost:4848) for the server version displayed in the console header or server status page.Affected if The version falls within any of these ranges: 4.1.2.191 to 4.1.2.191.45, 5.0.0 to 5.56.0, 6.0.0 to 6.7.0, or 6.2023.1 to 6.2023.10.
-
Verify Servlet Implementation module is in useConfirm that web applications are deployed and running on this Payara instance. Check for active web contexts via the admin console under 'Applications' > 'Deployments' or by querying deployed web modules via asadmin list-applications.Affected if Any web application or REST endpoint that performs server-side redirects is using the vulnerable servlet implementation.
-
Identify redirect-enabled endpointsReview application code and deployed WAR files for redirect handlers (HttpServletResponse.sendRedirect, forward, or redirect annotations). Check web.xml for redirect-servlet mappings or inspect deployed application's endpoint definitions.Affected if Any endpoint that accepts a redirect URL parameter and uses Payara's servlet container for redirection is potentially exploitable.
-
Test redirect behavior with external URLIf redirect endpoints are identified, attempt a request with an external domain in the redirect parameter (for example: https://yourserver/yourapp/redirect?url=http://malicious.example.com) and observe if the response Location header points to the external domain.Affected if The server allows redirection to arbitrary external domains instead of rejecting or restricting to internal URLs.
If the installed Payara version is within the affected ranges AND the server hosts applications with redirect functionality, the environment is vulnerable to CVE-2023-41699.
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 · scoped4.1.2.191.465.57.06.8.0
Upgrade Payara Platform to version 5.57.0, 4.1.2.191.46, 6.8.0, or 6.2023.11 or later. Alternatively, implement strict URL validation on all redirect endpoints to ensure redirects remain within trusted domains.
Upgrade to 4.1.2.191.46, 5.57.0, 6.8.0, or 6.2023.11 (or later) depending on your version branch
- Identify your currently installed Payara version by checking the server logs or administration console
- Determine which version branch you are on (4.1.2.191.x, 5.x, 6.0.x, or 6.2023.x)
- Download the appropriate fixed version for your branch: 4.1.2.191.46 or later for 4.1.2.191 line, 5.57.0 or later for 5.x line, 6.8.0 or later for 6.0.x line, or 6.2023.11 or later for 6.2023.x line
- Stop the Payara server
- Back up your current Payara installation including domain configurations
- Install the new version using the standard Payara upgrade process
- Restore your domain configurations from the backup
- Start the Payara server and verify the application functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41699 — 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-2023-41699 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