CVE-2021-27495
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 · uneditedYpsomed mylife Cloud, mylife Mobile Application:Ypsomed mylife Cloud,All versions prior to 1.7.2,Ypsomed mylife App,All versions prior to 1.7.5,he Ypsomed mylife Cloud reflects the user password during the login process after redirecting the user from a HTTPS endpoint to a HTTP endpoint.
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 mylife Cloud application reflects the user password in clear text during the login process when redirecting users from an HTTPS endpoint to an HTTP endpoint. This causes sensitive credential exposure through the URL, logs, and potentially referrer headers.
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.7.5< 1.7.2CVSS 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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 installed Ypsomed product versionLocate the version information for Ypsomed Mylife or Ypsomed Mylife Cloud in the application administration panel, about page, or installed software inventoryAffected if The version is below 1.7.5 for mylife or below 1.7.2 for mylife Cloud
-
Capture login redirect trafficUse a network traffic analyzer or browser developer tools to capture the network requests during a login attempt. Observe whether the login process redirects from HTTPS to HTTP after credentials are submittedAffected if A redirect from HTTPS to HTTP occurs during or after the login submission
-
Inspect URL for credential exposureExamine the browser address bar or captured network request URLs during the login redirect sequence. Look for the password parameter appearing in clear text within the URLAffected if The user password is visible as a clear text parameter in the URL after the redirect
-
Review server and proxy logsExamine web server access logs, application logs, or proxy logs for the login redirect sequence. Search for HTTP requests containing the password in the URL query stringAffected if Logs contain entries with the password visible in the URL path or query string
A user is affected if they are running a version below 1.7.5 (mylife) or below 1.7.2 (mylife Cloud) AND the login process redirects from HTTPS to HTTP with the password exposed in the URL.
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 data1.7.21.7.5
Upgrade to mylife Cloud version 1.7.2 or later and mylife Mobile App version 1.7.5 or later, and ensure the login flow maintains HTTPS throughout without redirecting to HTTP.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27495 — 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-2021-27495 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