CVE-2019-11011
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 · uneditedAkamai CloudTest before 58.30 allows remote code execution.
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 confidenceAkamai CloudTest versions prior to 58.30 contain a critical vulnerability allowing remote code execution. The CVSS 9.8 score indicates this is likely exploitable over the network without authentication, enabling attackers to execute arbitrary commands on affected systems.
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< 58.30CVSS 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.0/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 Akamai CloudTest installationCheck for Akamai CloudTest components on the system. Look for installation directories, services, or processes named 'CloudTest' or 'SOASTA' (the former company name). On Windows, check Program Files; on Linux/Unix, check common application paths like /opt/ or /usr/local/. Also check running processes for cloudtest-related entries.Affected if Akamai CloudTest is installed on the system
-
Identify CloudTest versionLocate the version information file or check the application UI. CloudTest typically stores version info in a 'version.txt' or similar file within the installation directory, or it can be accessed through the CloudTest administration console. Check the /opt/soasta directory or wherever CloudTest was installed.Affected if The installed version cannot be determined or is older than 58.30
-
Compare version against affected rangeIf version is found, compare it numerically to 58.30. Any version below 58.30 (including 58.20, 58.0, older releases) is affected. If the version shows 58.30 or higher, or if version information indicates a maintenance release like 58.30.1 or later, the system is NOT affected.Affected if Installed version is lower than 58.30 (for example: 58.20, 57.x, 56.x, etc.)
-
Verify network exposure of management interfaceCheck if the CloudTest management interface (typically ports 8080, 8443, or custom ports configured during installation) is exposed to the network. Review firewall rules, network configurations, and cloud security groups to determine if port 8080/8443 or the configured CloudTest ports are accessible from untrusted networks.Affected if CloudTest management interface is accessible from the internet or untrusted networks and version is below 58.30
The environment is affected if Akamai CloudTest is installed with a version lower than 58.30 and the management interface is network-accessible.
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 · scoped58.30
Upgrade Akamai CloudTest to version 58.30 or later to remediate the RCE vulnerability. If immediate upgrade is not feasible, restrict network access to CloudTest management interfaces and monitor for indicators of compromise.
58.30 or later
- Identify your current CloudTest version
- Contact Akamai support or access the CloudTest admin console to initiate an upgrade
- Upgrade to version 58.30 or later
- Verify the upgrade was successful by checking the CloudTest version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11011 — 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-11011 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