CVE-2022-46288
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 · uneditedOpen redirect vulnerability in DENSHI NYUSATSU CORE SYSTEM v6 R4 and earlier allows a remote unauthenticated attacker to redirect a user to an arbitrary web site and conduct a phishing attack by having a user to access a specially crafted URL.
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 confidenceOpen redirect vulnerability in DENSHI NYUSATSU CORE SYSTEM allows unauthenticated remote attackers to redirect users to arbitrary websites via specially crafted URLs, enabling phishing attacks. The application fails to properly validate redirect targets before forwarding users.
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<= 6= 6CVSS 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 the installed version of the bidding systemLocate the application version through the system administration interface, help menu, or version information file shipped with the software. For web applications, check the login page source or error messages for version disclosure.Affected if The installed version is 6 or lower (version 6, 5.x, 4.x, etc.)
-
Locate redirect-capable URL parametersReview application URLs for common redirect parameter names such as 'redirect', 'url', 'next', 'target', 'dest', 'goto', or 'return_url'. These are often found in login, logout, and navigation endpoints.Affected if The application URL contains parameters that control where users are redirected after an action
-
Test redirect validation with an arbitrary external domainModify a suspected redirect parameter to point to an external domain (example: '?redirect=https://example.com'). Submit the request and observe if the application allows navigation to the untrusted domain without blocking or sanitizing it.Affected if The application redirects to the arbitrary domain specified in the parameter rather than rejecting it or restricting to internal paths
-
Verify redirect occurs without authenticationSend the crafted redirect URL to an unauthenticated user (such as accessing the login page with a redirect parameter). Confirm the redirect happens before any authentication takes place.Affected if The open redirect triggers without requiring authentication, allowing phishing attacks on any user
If the system is DENSHI NYUSATSU CORE SYSTEM or Jacic Electronic Bidding Core System version 6 or below and uses redirect parameters in URLs, the application is likely affected by this open redirect vulnerability.
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 dataImplement strict validation of redirect URLs to ensure they point to trusted domains or paths within the application. Use an allowlist approach for permitted redirect destinations.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46288 — 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-46288 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