CVE-2014-4631
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 · uneditedRSA Adaptive Authentication (On-Premise) 6.0.2.1 through 7.1 P3, when using device binding in a Challenge SOAP call or using the RSA Adaptive Authentication Integration Adapters with Out-of-Band Phone (Authentify) functionality, conducts permanent device binding even when authentication fails, which allows remote attackers to bypass authentication.
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 confidenceRSA Adaptive Authentication (On-Premise) versions 6.0.2.1 through 7.1 P3 permanently binds a device to a user account during Challenge SOAP calls or when using Out-of-Bound Phone (Authentify) functionality, even when authentication fails. This allows an attacker to repeatedly trigger failed authentication attempts, causing unauthorized device binding that can later be exploited to bypass authentication controls.
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.0.2.1= 7.0= 7.1CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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 installed RSA Adaptive Authentication versionCheck the product version through the admin console, configuration files, or installation metadata. Common locations include version.info files, the system status page, or the about section in the admin interface.Affected if The installed version is 6.0.2.1, 7.0, or any 7.1.x release through 7.1 P3.
-
Verify Challenge SOAP endpoint configurationReview the SOAP service configuration files and web service settings to determine if Challenge SOAP calls are enabled and accessible.Affected if Challenge SOAP endpoints are exposed and enabled in the environment.
-
Confirm Authentify integration is activeExamine the integration settings or configuration files related to Out-of-Band Phone (Authentify) functionality to see if this feature is configured and active.Affected if Authentify/Out-of-Bound Phone functionality is enabled in the system.
-
Review device binding audit logsSearch authentication and device binding logs for patterns of failed authentication attempts followed by device bindings, particularly from unexpected sources or IP addresses.Affected if Device bindings exist that were created during failed authentication attempts or from unauthorized sources.
A user is affected if they run RSA Adaptive Authentication On-Premise versions 6.0.2.1 through 7.1 P3 with Challenge SOAP calls or Authentify functionality enabled, as these features allow unauthorized device binding during failed authentication.
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 dataUpgrade to RSA Adaptive Authentication (On-Premise) version 7.2 or later, or apply the vendor-supplied patch for this issue. If immediate patching is not possible, disable device binding in Challenge SOAP calls and review the Authentify integration configuration.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-4631 — 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-2014-4631 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