Security readout for executives and security teams
Plain-English summary
CVE-2018-11517 is an information disclosure issue in mySCADA myPRO 7. A remote party may enumerate ProjectIDs through the myPRO service, exposing project identifiers that could help map or target an industrial control environment.
Executive priority
Treat this as a containment and visibility issue, especially in operational technology environments. It may not directly grant control, but exposed project identifiers can reduce attacker effort and support follow-on targeting.
Technical view
The CVE description says remote attackers can discover all ProjectIDs by probing the prj parameter against the myPRO service on TCP port 11010. Public sources do not provide CVSS, CWE, authentication context, affected build ranges, or a named vendor fix.
Likely exposure
Exposure is most likely where mySCADA myPRO 7 service port 11010 is reachable from untrusted networks, remote sites, vendor access paths, or the internet.
Exploitation context
The CVE is not listed as KEV in the supplied bundle. Public references include proof-of-concept-oriented material, but the bundle does not establish active exploitation in the wild.
Researcher notes
Evidence is limited. The CVE record identifies ProjectID enumeration in mySCADA myPRO 7, but does not include CVSS, CWE, authentication requirements, complete affected versions, or remediation details. Avoid assuming exploit prevalence beyond the cited references.
Mitigation direction
- Identify any mySCADA myPRO 7 deployments and service exposure.
- Restrict TCP port 11010 to trusted management networks only.
- Remove internet exposure through firewall, VPN, or segmentation controls.
- Check mySCADA vendor guidance for supported fixes or upgrade paths.
- Monitor logs for repeated ProjectID probing patterns.
Validation and detection
- Confirm whether mySCADA myPRO 7 is present in the environment.
- Review firewall rules and remote access paths for TCP port 11010.
- Verify service access is limited to authorized management hosts.
- Check vendor advisories or support channels for fixed versions.
- Review network logs for unusual repeated myPRO service requests.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2018-11517 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.emreovunc.com/blog/en/mypro_enum_projectid.rbCVE reference · x_refsource_MISC
- https://github.com/EmreOvunc/mySCADA-myPRO-7-projectID-DisclosureCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.