CVE-2025-6098
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 · uneditedA vulnerability was found in UTT 进取 750W up to 5.0. It has been classified as critical. This affects the function strcpy of the file /goform/setSysAdm of the component API. The manipulation of the argument passwd1 leads to buffer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceBuffer overflow vulnerability in UTT 进取 750W power supply web interface (/goform/setSysAdm) allows remote attackers to overflow the passwd1 argument via unsafe strcpy function, potentially enabling arbitrary code execution or credential manipulation.
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.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 device modelCheck the physical device label or access the web interface to confirm the model is UTT 进取 750W power supplyAffected if Device is not a UTT 进取 750W power supply, then not affected
-
Check firmware versionAccess the device web interface or administrative panel and locate the firmware version information. Compare against the affected range: <= 5.0Affected if Firmware version is 5.0 or lower, indicating a potentially vulnerable version
-
Verify web interface accessibilityDetermine if the device web interface (port 80/443) is reachable from network segments. Use a browser or curl to access the interface URLAffected if Web interface is accessible from untrusted network segments, increasing exposure to the vulnerability
-
Confirm vulnerable endpoint existenceAttempt to access the /goform/setSysAdm endpoint via HTTP POST request with test data in the passwd1 parameter. A vulnerable device will accept the request without proper bounds checkingAffected if The /goform/setSysAdm endpoint responds and accepts the passwd1 parameter without rejecting oversized input
-
Check if remote management is enabledIn the device administrative interface, locate settings for remote/web-based management and confirm whether it is enabledAffected if Remote management interface is enabled, allowing potential exploitation of the buffer overflow
If the device is a UTT 进取 750W with firmware version 5.0 or lower and has its web interface accessible, the environment is likely affected by this vulnerability.
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 · scopedSince vendor did not respond, pursue network segmentation to isolate the device, disable remote management interfaces if not required, and contact vendor through alternate channels or consider device replacement if no firmware patch becomes available.
- Isolate the affected UTT 进取 750W router on a restricted network segment or VLAN to limit exposure to untrusted networks.
- If the device supports it, disable the vulnerable /goform/setSysAdm API endpoint or restrict access to trusted IP addresses only.
- Monitor network traffic for attempts to exploit the buffer overflow via the setSysAdm endpoint.
- Consider replacing the affected router with an actively supported model from a vendor that provides regular security updates.
- Implement network intrusion detection/prevention systems (IDS/IPS) to detect exploitation attempts.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6098 — 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-6098 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