dbcve.org
E RecruitingApplication · Sap

CVE-2017-14511

HIGH · 7.5 CVSS v3.0 Published 2017-09-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
An issue was discovered in SAP E-Recruiting (aka ERECRUIT) 605 through 617. When an external applicant registers to the E-Recruiting application, he/she receives a link by email to confirm access to the provided email address. However, this measure can be bypassed and attackers can register and confirm email addresses that they do not have access to (candidate_hrobject is predictable and corr_act_guid is improperly validated). Furthermore, since an email address can be registered only once, an attacker could prevent other legitimate users from registering. This is SAP Security Note 2507798.

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 confidence

SAP E-Recruiting versions 605-617 contains an email confirmation bypass vulnerability. The candidate_hrobject ID is generated predictably, and the corr_act_guid (correlation action GUID) is improperly validated, allowing attackers to confirm email addresses they do not own by predicting these values and bypassing the email verification step. This enables unauthorized account registration and prevents legitimate users from registering using their email.

MitigationApply SAP Security Note 2507798 which implements cryptographically random GUIDs for candidate_hrobject and corr_act_guid, adds proper validation checks, and ensures one-time-use tokens for email confirmation. Also review registration logs for suspicious activity.

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
E RecruitingApplication
Affected:= 605= 606= 616= 617

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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 SAP E-Recruiting version
    Access SAP system information transaction code SAINT or search for version details in SAP E-Recruiting system documentation. Look for the exact version number in the SAP E-Recruiting component.
    Affected if The installed version is 605, 606, 616, or 617 exactly as listed in the affected versions.
  2. Confirm candidate registration portal is accessible
    Navigate to the SAP E-Recruiting candidate registration URL or job portal interface that handles new user signup and email verification.
    Affected if The candidate registration feature is enabled and accessible to unauthenticated users.
  3. Review email confirmation logs for suspicious patterns
    Access SAP E-Recruiting audit logs or transaction code SLG1 for object ERECRUITING and subobject EMAIL_CONFIRM. Look for multiple confirmation attempts or unexpected email address confirmations.
    Affected if Logs show email confirmations occurring for addresses not initiated by the legitimate user, or duplicate confirmation attempts.
  4. Check for duplicate email registrations
    Query the SAP E-Recruiting candidate database table (commonly HRP1000 or similar candidate tables) for records where the same email address appears multiple times with different candidate IDs.
    Affected if The same email address is registered to multiple candidate_hrobject IDs, indicating potential exploitation.
  5. Verify GUID predictability
    Submit multiple test candidate registrations and observe the candidate_hrobject ID and corr_act_guid values in the confirmation links. Check if IDs follow a sequential or predictable pattern.
    Affected if The candidate_hrobject IDs are sequential or the corr_act_guid values can be predicted based on observed patterns.

A defender is affected if SAP E-Recruiting version is exactly 605, 606, 616, or 617 AND the candidate registration portal is accessible and email confirmations can be triggered with predictable IDs.

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 SAP Security Note 2507798 which implements cryptographically random GUIDs for candidate_hrobject and corr_act_guid, adds proper validation checks, and ensures one-time-use tokens for email confirmation. Also review registration logs for suspicious activity.

Fix this in E Recruiting Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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