LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36660: paxswill EVE Ship Replacement Program User Information api.py information disclosure

A vulnerability was found in paxswill EVE Ship Replacement Program 0.12.11. It has been rated as problematic. This issue affects some unknown processing of the file src/evesrp/views/api.py of the component User Information Handler. The manipulation leads to information disclosure. The attack may be initiated remotely. Upgrading to version 0.12.12 is able to address this issue. The patch is named 9e03f68e46e85ca9c9694a6971859b3ee66f0240. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-220211.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-36660 is an information disclosure issue in paxswill EVE Ship Replacement Program 0.12.11. A remote, low-privileged user may be able to access user information through the API handling code. The vendor-fixed release is 0.12.12.

Executive priority

Treat this as a moderate confidentiality risk. It does not indicate system takeover or service disruption, but exposed user information can create privacy, trust, and operational concerns. Prioritize remediation for internet-facing or broadly accessible deployments.

Technical view

The issue is mapped to CWE-200 and affects src/evesrp/views/api.py in the User Information Handler. CVSS 3.1 is 4.3: network reachable, low attack complexity, low privileges required, no user interaction, and low confidentiality impact only.

Likely exposure

Exposure appears limited to organizations running EVE Ship Replacement Program 0.12.11, especially where the application API is reachable by users or the network. The source bundle provides no CPEs and no broader affected version range.

Exploitation context

The sources say remote initiation is possible and the CVSS vector requires low privileges. The CVE is not listed as KEV, and the provided sources do not state active exploitation or public weaponized exploitation.

Researcher notes

Public details are sparse: the affected file and handler are identified, but the exact vulnerable processing path is not described in the bundle. Avoid assuming more affected versions or exploitability beyond CVSS PR:L, remote reachability, and the named 0.12.12 fix.

Mitigation direction

  • Upgrade EVE Ship Replacement Program to version 0.12.12.
  • Apply or verify patch commit 9e03f68e46e85ca9c9694a6971859b3ee66f0240.
  • If upgrade timing is unclear, check current vendor guidance before choosing compensating controls.
  • Limit API access to trusted authenticated users where operationally feasible.

Validation and detection

  • Inventory deployments and confirm whether version 0.12.11 is present.
  • Verify deployed code includes the referenced api.py patch commit.
  • Confirm the running application reports or matches release 0.12.12 after upgrade.
  • Review user information API behavior for least-privilege data exposure.
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 · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-2020-36660 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
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A: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
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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2020-36660Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
paxswillEVE Ship Replacement Program0.12.11Listed
Weakness

CWE details

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

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.