CVE-2024-45982
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 · uneditedA host header injection vulnerability in scheduleR v0.0.18 allows attackers to obtain the password reset token via user interaction with a crafted password reset link. This allows attackers to arbitrarily reset other users' passwords and compromise their accounts.
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 confidenceA host header injection vulnerability in scheduleR v0.0.18 allows attackers to manipulate the Host header in password reset requests, causing the application's password reset tokens to be transmitted to attacker-controlled domains when users interact with crafted reset links. This enables complete account takeover of any targeted user.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify scheduleR versionLocate the installed version of scheduleR by examining application metadata files such as package.json, version configuration, or the application's version endpoint. Compare the installed version to the affected version 0.0.18.Affected if The installed version is exactly 0.0.18
-
Confirm password reset is enabledVerify that the password reset functionality is enabled and accessible in the application. Check whether users can request password reset links through the application interface or API.Affected if Password reset functionality is enabled and operational
-
Examine password reset link generationInspect the code or configuration responsible for generating password reset URLs. Look for where the reset link hostname is determined - check if it directly uses the incoming HTTP Host header value without validation or whitelisting.Affected if Password reset links are generated using the Host header from incoming requests without strict validation
-
Check for Host header validationReview the application's security configuration or middleware to determine if there is any validation, whitelist, or hardcoding of allowed hostnames. Look for any Host header filtering logic in the web server or application layer.Affected if There is no strict Host header validation or whitelist configured for password reset operations
You are affected if scheduleR version 0.0.18 is installed AND password reset is enabled AND the reset link generation relies on the HTTP Host header without validation.
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 Host header validation/whitelisting and replace Host-dependent URL generation with hardcoded, verified domain values for password reset links.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45982 — 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-2024-45982 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