LiveActive security incident?Get immediate response
CVE Record

CVE-2017-20120: TrueConf Server cross-site request forgery

A vulnerability classified as problematic was found in TrueConf Server 4.3.7. This vulnerability affects unknown code of the file /admin/service/stop/. The manipulation leads to cross-site request forgery. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

TrueConf Server 4.3.7 has a CSRF issue that could let an attacker trick a logged-in user into sending an unintended administrative request. The public description points to the service stop endpoint, but does not document confirmed real-world exploitation or a vendor fix. Business urgency is moderate where this version is still used.

Executive priority

Handle during normal vulnerability remediation unless the server is internet-exposed, operationally critical, or no longer supported. The risk is not shown as actively exploited, but public disclosure and administrative action exposure justify timely inventory and upgrade review.

Technical view

CVE-2017-20120 is a CWE-352 cross-site request forgery in TrueConf Server 4.3.7 affecting /admin/service/stop/. CVSS 3.1 is 4.3, AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N. The bundle states public exploit disclosure, but provides no code-level details, patch version, or vendor advisory.

Likely exposure

Exposure is most relevant to organizations still running TrueConf Server 4.3.7, especially where administrative sessions are reachable from users' browsers. The issue requires user interaction and appears limited to low integrity impact in the provided CVSS data.

Exploitation context

The source bundle says an exploit was publicly disclosed and may be used. It does not show CISA KEV listing, active exploitation, or confirmed incident reporting. Treat this as publicly known but not source-confirmed as actively exploited.

Researcher notes

Evidence is thin: affected version, endpoint path, CWE, CVSS, and public exploit disclosure are provided, but patch status and exact vulnerable logic are not. Avoid broad product assumptions beyond TrueConf Server 4.3.7.

Mitigation direction

  • Identify any TrueConf Server 4.3.7 deployments.
  • Check TrueConf guidance for fixed versions or configuration mitigations.
  • Restrict administrative interface exposure to trusted networks and users.
  • Review CSRF protections and session controls around administrative actions.
  • Prioritize replacement or upgrade if the version is unsupported.

Validation and detection

  • Confirm product and version from asset inventory or server administration records.
  • Verify whether administrative endpoints are reachable from untrusted networks.
  • Check whether compensating controls limit browser access to administration paths.
  • Review change logs or vendor guidance for a named fix.
  • Document whether the system is still business-critical or can be retired.
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 · medium confidence lookup

CWE-352: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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-2017-20120 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:N/UI:R/S:U/C:N/I:L/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
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
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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
TrueConfServer4.3.7Listed
Weakness

CWE details

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

CWE-352 · source CWE mapping

Cross-Site Request Forgery (CSRF)

Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.