LiveActive security incident?Get immediate response
CVE Record

CVE-2011-10014: GTA SA-MP server.cfg Buffer Overflow

GTA San Andreas Multiplayer (SA-MP) server version 0.3.1.1 is vulnerable to a stack-based buffer overflow triggered by parsing a malformed server.cfg configuration file. The vulnerability allows local attackers to execute arbitrary code when the server binary (samp-server.exe) processes a crafted echo directive containing excessive input. The original 'sa-mp.com' site is defunct, but the community maintains mirrors and forks that may be vulnerable.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A legacy GTA San Andreas Multiplayer server can be compromised if it loads a malicious server.cfg file. The issue is local and configuration-driven, so urgency depends on whether anyone can alter server files or supply configs.

Executive priority

Treat as high priority only if legacy SA-MP infrastructure exists. The business risk is arbitrary code execution on the server host after malicious configuration handling, not broad unauthenticated internet exploitation.

Technical view

SA-MP server 0.3.1.1 has a stack-based buffer overflow while parsing a malformed server.cfg echo directive. The CVSS v4 vector marks local access, low complexity, attacker preparation, and user action, with high impact across confidentiality, integrity, and availability.

Likely exposure

Likely limited to organizations or communities still running SA-MP 0.3.1.1, old mirrored binaries, or unverified forks. Exposure increases where server configuration files are shared, downloaded, or writable by untrusted users.

Exploitation context

Public exploit references exist in Exploit-DB and Metasploit. The bundle does not show CISA KEV listing or active exploitation evidence, so active exploitation should not be assumed.

Researcher notes

Evidence supports CWE-121 stack overflow in server.cfg parsing for SA-MP 0.3.1.1. Patch status is not established in the provided sources, and the original site is defunct. Validate forks separately rather than assuming inheritance.

Mitigation direction

  • Do not run untrusted or externally supplied server.cfg files.
  • Restrict write access to SA-MP server directories and configuration files.
  • Check community fork or maintainer guidance for a fixed replacement build.
  • Retire SA-MP 0.3.1.1 where operationally possible.
  • Run legacy game servers in isolated, low-privilege environments.

Validation and detection

  • Inventory any SA-MP servers and confirm exact binary versions.
  • Review server.cfg provenance and recent modification history.
  • Verify only trusted administrators can modify configuration files.
  • Check whether deployed forks inherited the vulnerable parser behavior.
  • Search for vendor or community advisories before applying replacements.
Prepared
Confidence
medium
Sources
6

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-121: 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2011-10014 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:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

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
5Source 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:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

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

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

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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SA-MP TeamSan Andreas Multiplayer0.3.1.1unknown
Weakness

CWE details

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

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.