CVE-2022-0637
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 · uneditedopen redirect in pollbot (pollbot.services.mozilla.com) in versions before 1.4.6
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 confidenceAn open redirect vulnerability exists in pollbot (pollbot.services.mozilla.com) that allows attackers to craft malicious URLs which redirect users to arbitrary external sites. This occurs due to insufficient validation of redirect parameters, enabling phishing and social engineering attacks.
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.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Pollbot is running in your environmentCheck running processes or services for 'pollbot', or look for the application in your deployment inventory. If Pollbot is deployed as a web service, verify it is accessible via its configured hostname or localhost port.Affected if Pollbot is not deployed or is not running in your environment.
-
Determine the installed Pollbot versionRun the command 'pollbot --version' if the CLI is available, or check the version from the running service's /health or /version endpoint. If deployed via package manager, run 'pip show pollbot' or check the installed package version.Affected if You cannot determine the version or no version information is returned.
-
Compare installed version against affected rangeCompare the version you found in step 2 to the affected range: versions prior to 1.4.6 are vulnerable. For example, 1.4.5, 1.4.0, 1.3.0 are all in the affected range.Affected if The installed version is lower than 1.4.6 (e.g., 1.4.5, 1.3.2, etc.).
-
Verify the web redirect feature is accessiblePollbot exposes a web interface that processes redirect parameters. Confirm the service is network-accessible and check if endpoints handling redirect or 'next' parameters exist in the application routes.Affected if The service is accessible and processes user-controlled redirect parameters.
Your environment is affected if Pollbot is running with a version lower than 1.4.6 and the web service is accessible, since the insufficient redirect validation vulnerability would be exploitable.
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.6
Upgrade pollbot to version 1.4.6 or later. If immediate patching is not possible, implement URL allowlist validation for redirect targets to prevent redirection to untrusted domains.
Pollbot 1.4.6
- Check the current installed version of Pollbot
- Upgrade Pollbot to version 1.4.6 or later
- Verify the upgrade was successful by checking the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0637 — 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-2022-0637 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