CVE-2022-30028
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 · uneditedDradis Professional Edition before 4.3.0 allows attackers to change an account password via reusing a password reset token.
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 confidenceDradis Professional Edition before version 4.3.0 contains an insecure password reset implementation where the password reset token is not invalidated after successful use. This allows an attacker who obtains a valid reset token (e.g., through interception or guessable tokens) to reuse the same token multiple times to change the account password arbitrarily.
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< 4.3.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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.
-
Determine Dradis Professional Edition versionAccess the Dradis web interface and navigate to Help > About, or check the installed package version using the package manager if installed locally (e.g., rpm -q dradis-pro or dpkg -l | grep dradis)Affected if Version is below 4.3.0
-
Confirm password reset feature is enabledCheck if the password reset functionality is accessible at /users/password or /password/reset on the Dradis instance. This is typically enabled by default in standard installations.Affected if Password reset endpoint is accessible and functional
-
Review password reset token handlingIf you have access to the application logs or source code, examine the password reset controller to verify whether tokens are invalidated after a successful password change. Look for code that deletes or marks the token as used after the password is updated.Affected if No token invalidation logic is present after password reset completion
The environment is affected if Dradis Professional Edition version is below 4.3.0 and the password reset feature is accessible.
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 · scoped4.3.0
Upgrade to Dradis Professional Edition 4.3.0 or later, which includes proper token invalidation after single use.
Dradis Professional Edition 4.3.0
- 1. Back up your current Dradis Professional Edition installation and database.
- 2. Review the Dradis release notes for version 4.3.0 to understand any changes.
- 3. Upgrade Dradis Professional Edition to version 4.3.0 or later.
- 4. After upgrading, verify that the password reset functionality works correctly.
- 5. Consider invalidating any existing password reset tokens as a precautionary measure.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.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,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30028 — 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-30028 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