What is the CVSS score of CVE-2013-7247?

CVE-2013-7247 has a CVSS 2.0 base score of 5.0 (Medium). CVSS vector: AV:N/AC:L/Au:N/C:P/I:N/A:N. EPSS exploitation probability: 17.2%.

Is there a public PoC exploit available for CVE-2013-7247?

Yes, a public proof-of-concept exploit is available for CVE-2013-7247. Prioritise patching immediately. EPSS: 17.2%.

Ts 550 Evo Firmware CVE-2013-7247

MEDIUM

Permissions, Privileges, and Access Controls (CWE-264)

2014-01-26 cve@mitre.org

Privilege Escalation Ts 550 Evo Firmware Ts 550 Evo

5.0

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

5.0 MEDIUM

AV:N/AC:L/Au:N/C:P/I:N/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:L/Au:N/C:P/I:N/A:N

Attack Vector

Network

Attack Complexity

Low

Confidentiality

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Jan 26, 2014 - 01:55 cve.org

MEDIUM 5.0

DescriptionCVE.org

cgi-bin/tsaws.cgi in Franklin Fueling Systems TS-550 evo with firmware 2.0.0.6833 and other versions before 2.4.0 allows remote attackers to discover sensitive information (user names and password hashes) via the cmdWebGetConfiguration action in a TSA_REQUEST.

AnalysisAI

cgi-bin/tsaws.cgi in Franklin Fueling Systems TS-550 evo with firmware 2.0.0.6833 and other versions before 2.4.0 allows remote attackers to discover sensitive information (user names and password. Rated medium severity (CVSS 5.0), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and EPSS exploitation probability 17.2%.

Technical ContextAI

This vulnerability is classified under CWE-264. cgi-bin/tsaws.cgi in Franklin Fueling Systems TS-550 evo with firmware 2.0.0.6833 and other versions before 2.4.0 allows remote attackers to discover sensitive information (user names and password hashes) via the cmdWebGetConfiguration action in a TSA_REQUEST. Affected products include: Franklinfueling Ts-550 Evo Firmware, Franklinfueling Ts-550 Evo. Version information: before 2.4.0.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.