LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25169: AMPPS 2.7 Denial of Service via Malformed Socket Connection

AMPPS 2.7 contains a denial of service vulnerability that allows remote attackers to crash the service by sending malformed data to the default HTTP port. Attackers can establish multiple socket connections and transmit invalid payloads to exhaust server resources and cause service unavailability.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

AMPPS 2.7 can be remotely crashed by malformed traffic sent to its default HTTP port. The business impact is service outage, not confirmed data theft or system takeover. Public exploit material is referenced, but the provided sources do not show active exploitation in the wild.

Executive priority

Prioritize remediation for any internet-facing AMPPS 2.7 system because unauthenticated attackers could cause outages. If AMPPS is only used in isolated development environments, urgency is lower but access should still be restricted and vendor guidance checked.

Technical view

CVE-2018-25169 affects AMPPS 2.7. A remote, unauthenticated attacker can establish multiple socket connections and send invalid payloads to exhaust server resources, causing denial of service. CVSS 4.0 score is 8.7, with high availability impact and no confidentiality or integrity impact stated.

Likely exposure

Exposure is most relevant where AMPPS 2.7 is reachable over a network, especially from the internet, on its default HTTP service. Internal development, staging, or lab systems may also be affected if accessible to untrusted users.

Exploitation context

The source bundle references ExploitDB content, indicating public exploit information exists. CISA KEV status is false in the provided data, and no cited source confirms active exploitation. The attack requires network access but no authentication or user interaction.

Researcher notes

Evidence supports a network-based denial-of-service issue in AMPPS 2.7 with public exploit reference. Sources do not identify a fixed version, patch, or active exploitation. Avoid assuming broader AMPPS versions are affected unless confirmed by vendor or CVE updates.

Mitigation direction

  • Identify any AMPPS 2.7 instances in production, development, and lab environments.
  • Check AMPPS vendor guidance for an update, fixed version, or supported mitigation.
  • Restrict AMPPS HTTP access to trusted networks only.
  • Avoid exposing AMPPS 2.7 directly to the internet.
  • Monitor affected services for repeated crashes or resource exhaustion.

Validation and detection

  • Confirm whether AMPPS 2.7 is installed anywhere in the environment.
  • Determine whether the AMPPS HTTP port is reachable from untrusted networks.
  • Review service logs for malformed connection patterns and unexplained crashes.
  • Verify compensating controls limit access to authorized users or networks.
  • Track vendor or advisory updates for remediation status.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cwe · low confidence lookup

CWE-1188: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-25169 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2018-25169Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AmppsAMPPS2.7Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1188 · source CWE mapping

Initialization of a Resource with an Insecure Default

Initialization of a Resource with an Insecure Default represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.