CVE-2022-45611
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 · uneditedAn issue was discovered in Fresenius Kabi PharmaHelp 5.1.759.0 allows attackers to gain escalated privileges via via capture of user login information.
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 confidenceThe Fresenius Kabi PharmaHelp 5.1.759.0 web application contains a privilege escalation vulnerability where attackers can capture user login information to gain elevated privileges. The mechanism of capture is not detailed, but it suggests a weakness in authentication, session management, or credential handling that allows unauthorized access to higher-privilege accounts.
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= 5.1.759.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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 the installed Fresenius Kabi PharmaHelp versionAccess the application's about page, check the login screen footer, or query the system information endpoint if available. Alternatively, check the firmware version displayed in the administration panel or system settings.Affected if The displayed version is exactly 5.1.759.0
-
Verify the web application build numberInspect the HTTP response headers from the application's login page or check the application manifest files on the server if you have file system access. Look for build identifiers in the response or static assets.Affected if The build number matches 759.0 or the exact version string 5.1.759.0 is present
-
Confirm firmware version via system administration interfaceLog into the administrative interface of PharmaHelp and navigate to System Information, Maintenance, or About sections. Document the firmware version displayed.Affected if The firmware version listed is 5.1.759.0 exactly
-
Review authentication configurationExamine the application's authentication configuration files or settings panel for session management parameters. Check if HTTPS is enforced on login endpoints by inspecting the protocol in use.Affected if The version is 5.1.759.0 AND the application uses HTTP instead of HTTPS for authentication endpoints, or uses default/insecure session tokens
You are affected if the Fresenius Kabi PharmaHelp firmware version is exactly 5.1.759.0 and the application handles user authentication with potential exposure of login credentials.
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 proper session management with secure token generation, enforce HTTPS for all authentication endpoints, and ensure credentials are not exposed or easily interceptable. Consider implementing multi-factor authentication and role-based access controls.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45611 — 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-45611 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