dbcve.org
Secure Entry ServerApplication · United Security Providers

CVE-2013-2764

MEDIUM · 6.1 CVSS v3.1 Published 2020-01-28
Fix available
A fix is available. Upgrade to 4.7.0 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
Secure Entry Server before 4.7.0 contains a URI Redirection vulnerability which could allow remote attackers to conduct phishing attacks due to HSP_AbsoluteRedirects being disabled by default.

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

Secure Entry Server before version 4.0 contains a URI redirection (open redirect) vulnerability. The HSP_AbsoluteRedirects setting is disabled by default, causing the server to use relative redirects that can be manipulated by attackers to redirect users to malicious sites for phishing attacks.

MitigationUpgrade Secure Entry Server to version 4.7.0 or later, or enable the HSP_AbsoluteRedirects setting to enforce absolute URL redirects and prevent manipulation of redirect targets.

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
Secure Entry ServerApplication
Affected:< 4.7.0

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 Secure Entry Server version
    Locate the installed version of United Security Providers Secure Entry Server. This is typically found in the server's about page, version file, or installation directory. Common locations include the administration console or a version.info file in the installation root.
    Affected if Installed version is lower than 4.7.0 (e.g., 4.6.x, 4.5.x, 4.0.x, or any version before 4.7.0)
  2. Locate HSP_AbsoluteRedirects setting
    Find the configuration file for Secure Entry Server that contains the HSP_AbsoluteRedirects parameter. This is typically in the server configuration directory, often named ses.config, web.config, or server.xml. Search for the string 'HSP_AbsoluteRedirects' within configuration files.
    Affected if The HSP_AbsoluteRedirects setting cannot be found in the configuration, indicating it uses the default disabled state
  3. Verify HSP_AbsoluteRedirects configuration value
    Examine the HSP_AbsoluteRedirects setting value. If present, confirm whether it is set to 'false', '0', 'disabled', or is absent (using default). If set to 'true', '1', or 'enabled', absolute redirects are enforced.
    Affected if HSP_AbsoluteRedirects is set to false, disabled, 0, or is not explicitly configured (using default disabled state)
  4. Test redirect behavior (optional confirmation)
    If accessible, send a request to the Secure Entry Server that triggers a redirect (such as a logout or post-login navigation) and examine the Location header in the HTTP response. Check whether the redirect URL is absolute (full URL starting with http:// or https://) or relative (path only).
    Affected if Redirect URLs in HTTP responses are relative paths rather than absolute URLs, confirming the vulnerable behavior

A user is affected if their Secure Entry Server version is below 4.7.0 AND the HSP_AbsoluteRedirects setting is disabled, not set, or set to a false value, allowing relative redirects that can be manipulated for phishing attacks.

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
Upgrade available Upgrade to 4.7.0 or later
Fixed in 4.7.0
Interim mitigation

Upgrade Secure Entry Server to version 4.7.0 or later, or enable the HSP_AbsoluteRedirects setting to enforce absolute URL redirects and prevent manipulation of redirect targets.

Fix this in Secure Entry Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

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