CVE-2019-13547
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 · uneditedAdvantech WISE-PaaS/RMM, Versions 3.3.29 and prior. There is an unsecured function that allows anyone who can access the IP address to use the function without authentication.
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 confidenceAdvantech WISE-PaaS/RMM versions 3.3.29 and prior contain an unauthenticated function accessible via the IP address that can be invoked by any remote attacker without credentials, resulting in critical unauthenticated access to the RMM platform.
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<= 3.3.29CVSS 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.
-
Confirm WISE-PaaS/RMM is installedCheck for the presence of Advantech WISE-PaaS/RMM software on the system, typically installed in C:\Program Files\Advantech\WISE-PaaS\RMM or similar directories. Look for running processes named WisePaaS.exe or RMM-related services.Affected if The software is present on the system.
-
Verify the installed versionLocate the version information in the installation directory, typically in a version.txt, about dialog, or the main executable properties. Compare the version number to the affected range <= 3.3.29.Affected if The installed version is 3.3.29 or lower.
-
Test for unauthenticated endpoint accessibilityFrom a remote system, attempt to access the RMM interface via HTTP/HTTPS using the IP address without providing any credentials. Look for successful HTTP responses (200 OK) that return application data or administrative functionality without being redirected to a login page.Affected if The interface returns authenticated content or functional responses without requiring login credentials.
-
Check network exposureReview firewall rules and network configuration to determine if the RMM web interface (typically ports 80, 443, or 8080) is exposed directly to untrusted networks or the public internet.Affected if The RMM ports are accessible from untrusted network segments or the internet without authentication.
A user is affected if WISE-PaaS/RMM version 3.3.29 or lower is installed AND the unauthenticated function is accessible from the network without 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 authentication and authorization controls on the exposed function, apply network segmentation to restrict access, and upgrade to a patched version if available beyond 3.3.29.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13547 — 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-2019-13547 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