MITRE ATT&CK T1190: Exploit Public-Facing Application
When to use this skill
Use this skill when the task involves T1190, Exploit Public-Facing Application, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.
Technique context
- ATT&CK domain: enterprise
- ATT&CK ID: T1190
- Technique name: Exploit Public-Facing Application
- Type: technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1190
- Tactics: initial-access
- Platforms: Containers, ESXi, IaaS, Linux, macOS, Network Devices, Windows
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.
Exploited applications are often websites/web servers, but can also include databases (like SQL), standard services (like SMB or SSH), network device administration and management protocols (like SNMP and Smart Install), and any other system with Internet-accessible open sockets.(Citation: NVD CVE-2016-6662)(Citation: CIS Multiple SMB Vulnerabilities)(Citation: US-CERT TA18-106A Network Infrastructure Devices 2018)(Citation: Cisco Blog Legacy Device Attacks)(Citation: NVD CVE-2014-7169) On ESXi infrastructure, adversaries may exploit exposed OpenSLP services; they may alternatively exploit exposed VMware vCenter servers.(Citation: Recorded Future ESXiArgs Ransomware 2023)(Citation: Ars Technica VMWare Code Execution Vulnerability 2021) Depending on the flaw being exploited, this may also involve Exploitation for Stealth or Exploitation for Client Execution.
If an application is hosted on cloud-based infrastructure and/or is containerized, then exploiting it may lead to compromise of the underlying instance or container. This can allow an adversary a path to access the cloud or container APIs (e.g., via the Cloud Instance Metadata API), exploit container host access via Escape to Host, or take advantage of weak identity and access management policies.
Adversaries may also exploit edge network infrastructure and related appliances, specifically targeting devices that do not support robust host-based defenses.(Citation: Mandiant Fortinet Zero Day)(Citation: Wired Russia Cyberwar)
For websites and databases, the OWASP top 10 and CWE top 25 highlight the most common web-based vulnerabilities.(Citation: OWASP Top 10)(Citation: CWE top 25)
Agent workflow
- Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.
- Load bundled resources as needed: use
references/technique-profile.json for structured metadata, references/detection-and-mitigation.md for triage and telemetry guidance, references/known-threat-context.md for ATT&CK relationship context, and templates/ for repeatable outputs.
- Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.
- Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
- Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
- Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.
Bundled resources
references/technique-profile.json: machine-readable ATT&CK metadata for this technique.
references/detection-and-mitigation.md: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.
references/known-threat-context.md: ATT&CK relationship context with attribution cautions.
templates/detection-brief.md: detection engineering brief template.
templates/hunt-plan.md: threat hunt plan template.
templates/incident-response-note.md: incident response note template.
templates/coverage-assessment.md: ATT&CK coverage assessment template.
scripts/render_brief.py: local helper that renders a Markdown defensive brief from technique-profile.json.
assets/output-schema.json: JSON schema for structured technique analysis outputs.
To generate a quick brief, run python scripts/render_brief.py --output brief.md from inside this skill directory, or adapt the templates directly.
Detection guidance
No ATT&CK detection guidance was present in the source STIX object.
Useful telemetry and data sources
- Not specified in the STIX object.
Mitigations to consider
- Application Isolation and Sandboxing
- Exploit Protection
- Filter Network Traffic
- Limit Access to Resource Over Network
- Network Segmentation
- Privileged Account Management
- Update Software
- Vulnerability Scanning
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- APT28 (intrusion-set)
- APT29 (intrusion-set)
- APT39 (intrusion-set)
- APT41 (intrusion-set)
- APT5 (intrusion-set)
- Agrius (intrusion-set)
- Anthropic AI-orchestrated Campaign (campaign)
- ArcaneDoor (campaign)
- Axiom (intrusion-set)
- BOLDMOVE (malware)
- BackdoorDiplomacy (intrusion-set)
- BlackByte (intrusion-set)
- BlackTech (intrusion-set)
- Blue Mockingbird (intrusion-set)
- C0017 (campaign)
- C0018 (campaign)
- C0027 (campaign)
- COATHANGER (malware)
- Cinnamon Tempest (intrusion-set)
- Cutting Edge (campaign)
Recommended output pattern
When responding with this skill, structure the answer as:
- Assessment: whether the evidence supports this ATT&CK mapping and why.
- Evidence: specific indicators, logs, behaviors, and assumptions.
- Detection: telemetry sources, analytic logic, and tuning considerations.
- Response: containment, eradication, recovery, and validation actions.
- Coverage gaps: missing logs, sensors, controls, or environmental details.
- References: include the ATT&CK URL and any user-provided evidence references.
ATT&CK contributors
- Praetorian
- Yossi Weizman, Azure Defender Research Team
- Don Le, Stifel Financial
1---2name: attack-ent-t1190-exploit-public-facing-application3description: "Analyze MITRE ATT&CK T1190 Exploit Public-Facing Application in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1190, Exploit Public-Facing Application, or enterprise ATT&CK. Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network."4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See https://attack.mitre.org/resources/terms-of-use/5metadata:6 source: https://skillmd.com/skills/santosomar/attack-ent-t1190-exploit-public-facing-application7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T119010 attack_stix_id: attack-pattern--3f886f2a-874f-4333-b794-aa6075009b1c11 attack_version: "2.8"12 attack_modified: "2025-10-24T17:48:41.788Z"13---1415# MITRE ATT&CK T1190: Exploit Public-Facing Application1617## When to use this skill1819Use this skill when the task involves T1190, Exploit Public-Facing Application, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.2021## Technique context2223- ATT&CK domain: enterprise24- ATT&CK ID: T119025- Technique name: Exploit Public-Facing Application26- Type: technique27- ATT&CK URL: https://attack.mitre.org/techniques/T119028- Tactics: initial-access29- Platforms: Containers, ESXi, IaaS, Linux, macOS, Network Devices, Windows30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.3738Exploited applications are often websites/web servers, but can also include databases (like SQL), standard services (like SMB or SSH), network device administration and management protocols (like SNMP and Smart Install), and any other system with Internet-accessible open sockets.(Citation: NVD CVE-2016-6662)(Citation: CIS Multiple SMB Vulnerabilities)(Citation: US-CERT TA18-106A Network Infrastructure Devices 2018)(Citation: Cisco Blog Legacy Device Attacks)(Citation: NVD CVE-2014-7169) On ESXi infrastructure, adversaries may exploit exposed OpenSLP services; they may alternatively exploit exposed VMware vCenter servers.(Citation: Recorded Future ESXiArgs Ransomware 2023)(Citation: Ars Technica VMWare Code Execution Vulnerability 2021) Depending on the flaw being exploited, this may also involve [Exploitation for Stealth](https://attack.mitre.org/techniques/T1211) or [Exploitation for Client Execution](https://attack.mitre.org/techniques/T1203).3940If an application is hosted on cloud-based infrastructure and/or is containerized, then exploiting it may lead to compromise of the underlying instance or container. This can allow an adversary a path to access the cloud or container APIs (e.g., via the [Cloud Instance Metadata API](https://attack.mitre.org/techniques/T1552/005)), exploit container host access via [Escape to Host](https://attack.mitre.org/techniques/T1611), or take advantage of weak identity and access management policies.4142Adversaries may also exploit edge network infrastructure and related appliances, specifically targeting devices that do not support robust host-based defenses.(Citation: Mandiant Fortinet Zero Day)(Citation: Wired Russia Cyberwar)4344For websites and databases, the OWASP top 10 and CWE top 25 highlight the most common web-based vulnerabilities.(Citation: OWASP Top 10)(Citation: CWE top 25)4546## Agent workflow47481. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.492. Load bundled resources as needed: use `references/technique-profile.json` for structured metadata, `references/detection-and-mitigation.md` for triage and telemetry guidance, `references/known-threat-context.md` for ATT&CK relationship context, and `templates/` for repeatable outputs.503. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.514. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.525. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.536. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.5455## Bundled resources5657- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.58- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.59- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.60- `templates/detection-brief.md`: detection engineering brief template.61- `templates/hunt-plan.md`: threat hunt plan template.62- `templates/incident-response-note.md`: incident response note template.63- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.64- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.65- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6667To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6869## Detection guidance7071No ATT&CK detection guidance was present in the source STIX object.7273## Useful telemetry and data sources7475- Not specified in the STIX object.7677## Mitigations to consider7879- Application Isolation and Sandboxing80- Exploit Protection81- Filter Network Traffic82- Limit Access to Resource Over Network83- Network Segmentation84- Privileged Account Management85- Update Software86- Vulnerability Scanning8788## Known threat context8990Use these examples only as contextual leads, not as proof that an observed event is this technique:9192- APT28 (intrusion-set)93- APT29 (intrusion-set)94- APT39 (intrusion-set)95- APT41 (intrusion-set)96- APT5 (intrusion-set)97- Agrius (intrusion-set)98- Anthropic AI-orchestrated Campaign (campaign)99- ArcaneDoor (campaign)100- Axiom (intrusion-set)101- BOLDMOVE (malware)102- BackdoorDiplomacy (intrusion-set)103- BlackByte (intrusion-set)104- BlackTech (intrusion-set)105- Blue Mockingbird (intrusion-set)106- C0017 (campaign)107- C0018 (campaign)108- C0027 (campaign)109- COATHANGER (malware)110- Cinnamon Tempest (intrusion-set)111- Cutting Edge (campaign)112113## Recommended output pattern114115When responding with this skill, structure the answer as:116117- Assessment: whether the evidence supports this ATT&CK mapping and why.118- Evidence: specific indicators, logs, behaviors, and assumptions.119- Detection: telemetry sources, analytic logic, and tuning considerations.120- Response: containment, eradication, recovery, and validation actions.121- Coverage gaps: missing logs, sensors, controls, or environmental details.122- References: include the ATT&CK URL and any user-provided evidence references.123124## ATT&CK contributors125126- Praetorian127- Yossi Weizman, Azure Defender Research Team128- Don Le, Stifel Financial