CVE-2018-3774
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 · uneditedIncorrect parsing in url-parse <1.4.3 returns wrong hostname which leads to multiple vulnerabilities such as SSRF, Open Redirect, Bypass Authentication Protocol.
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 confidenceThe url-parse library before version 1.4.3 incorrectly parses URLs and returns the wrong hostname. This parsing flaw can be exploited to perform Server-Side Request Forgery (SSRF) attacks, execute open redirects, or bypass authentication mechanisms.
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< 1.4.3CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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.
-
Locate url-parse in your project dependenciesSearch for url-parse in package.json, package-lock.json, yarn.lock, or requirements files. Also check node_modules directory for the url-parse folder.Affected if url-parse is listed as a dependency or exists in node_modules with a version below 1.4.3
-
Determine the installed version of url-parseRun 'npm list url-parse' or 'yarn list url-parse' to see the installed version. Alternatively, check the package.json file inside node_modules/url-parse/package.json for the 'version' field.Affected if The reported version is less than 1.4.3 or no version is shown (indicating an old unversioned copy)
-
Identify code that uses url-parse for URL parsingSearch your codebase for imports or requires of 'url-parse' and usage patterns such as urlParse(url) or new UrlParse(url). Look for where user-supplied URLs or URL parameters are passed to this function.Affected if url-parse is used to parse URLs that contain user-controlled input such as request parameters, API endpoints, or redirect targets
-
Check for SSRF-prone functionalityReview code that makes HTTP requests based on parsed URLs, such as fetch, axios, request, or http.get calls where the URL comes from url-parse output.Affected if Your application uses url-parse to extract URLs from user input and then makes network requests to those URLs
-
Check for authentication and redirect logicReview code that uses url-parse output for authentication decisions, session handling, or redirect destinations (e.g., response.redirect or res.location).Affected if url-parse is used to determine redirect targets or authentication scopes based on parsed hostnames
You are affected if url-parse version below 1.4.3 is installed and your code uses it to parse URLs from untrusted sources.
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.
dbcve · scoped1.4.3
Upgrade url-parse to version 1.4.3 or later to resolve the hostname parsing vulnerability.
url-parse >= 1.4.3
- Update the url-parse package to version 1.4.3 or higher. For npm, run: npm install url-parse@^1.4.3. For yarn, run: yarn add url-parse@^1.4.3
- After updating, verify the installed version by running npm list url-parse or checking package.json
- Test your application to ensure URL parsing works correctly and the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-3774 — 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-2018-3774 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