CVE-2025-61120
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 · uneditedAG Life Logger Android App version v1.0.2.72 and before (package name com.donki.healthy), developed by IO FIT, K.K., contains improper access control vulnerabilities. Exposed credentials in traffic may allow attackers to misuse cloud resources, and predictable verification codes make brute-force account logins feasible. Successful exploitation could result in account compromise, privacy breaches, and abuse of cloud resources.
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 AG Life Logger Android app (com.donki.healthy) versions v1.0.2.72 and prior suffer from improper access control, allowing exposed credentials captured from network traffic to be leveraged for unauthorized access to cloud resources. Additionally, predictable verification codes enable brute-force attacks against account logins, leading to potential account compromise and privacy breaches.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 AG Life Logger app is installedCheck Android device for app with package name com.donki.healthy. Use settings > apps or run: adb shell pm list packages | grep donki.healthyAffected if Package com.donki.healthy exists on the device
-
Determine installed app versionNavigate to Android Settings > Apps > AG Life Logger > Version information, or use: adb shell dumpsys package com.donki.healthy | grep versionNameAffected if Version displayed is v1.0.2.72 or any version prior to it
-
Assess exposure to network credential theftThe vulnerability allows exposed credentials from network traffic to be leveraged. This is inherent to the app version if affected - the app does not implement proper TLS certificate pinning, allowing credentials to be captured in transit.Affected if App version is v1.0.2.72 or prior and the app is used to transmit credentials over network
-
Assess exposure to verification code brute-forceThe vulnerability involves predictable verification codes. This is inherent to the app version if affected - the app uses predictable codes rather than cryptographically secure OTP.Affected if App version is v1.0.2.72 or prior and the app uses verification codes for authentication
User is affected if the AG Life Logger app (com.donki.healthy) is installed at version v1.0.2.72 or any prior version, as both credential exposure via network traffic and predictable verification codes apply to these versions.
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 TLS with certificate pinning to protect credentials in transit, replace predictable verification codes with cryptographically secure one-time passwords (OTP) with rate limiting and account lockout policies.
- Consultation5.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61120 — 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-2025-61120 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