CVE-2013-2073

NONECVSS 0.0

0.0

Transifex command-line client before 0.9 does not validate X.509 certificates, which allows man-in-the-middle attackers to spoof a Transifex server via an arbitrary certificate.

CVSS v3: —
EG Score: 0.0(none)
EPSS: 35.6%
KEV: Not listed

Published

May 2, 2014

Last Modified

May 6, 2026

References (6)

secalert@redhathttp://blog.transifex.com/post/51072109836/new-version-of-the-transifex-client-has-been-released
secalert@redhathttp://www.openwall.com/lists/oss-security/2013/05/22/14
secalert@redhathttps://bugzilla.redhat.com/show_bug.cgi?id=952194
af854a3a-2127-422b-91ae-364da2661108http://blog.transifex.com/post/51072109836/new-version-of-the-transifex-client-has-been-released
af854a3a-2127-422b-91ae-364da2661108http://www.openwall.com/lists/oss-security/2013/05/22/14
af854a3a-2127-422b-91ae-364da2661108https://bugzilla.redhat.com/show_bug.cgi?id=952194

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-20Improper Input Validation

Data Freshness Timeline

(refreshed 14× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-06 13:45 UTCepss_batch
2026-06-06 13:45 UTCepss_batch
2026-06-05 22:44 UTCepss_batch
2026-06-05 22:44 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-02 20:10 UTCepss_batch
2026-06-02 20:10 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 19:10 UTCEG score recompute
2026-05-28 19:10 UTCGHSA enrichment
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch

Frequently asked(4)

What is CVE-2013-2073?

CVE-2013-2073 is a none vulnerability published on May 2, 2014. Transifex command-line client before 0.9 does not validate X.509 certificates, which allows man-in-the-middle attackers to spoof a Transifex server via an arbitrary certificate.

When was CVE-2013-2073 disclosed?

CVE-2013-2073 was first published in the National Vulnerability Database on May 2, 2014, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2013-2073 actively exploited?

CVE-2013-2073 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2013-2073?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-2073, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2013-2073

Explore →

Is Your Infrastructure Affected by CVE-2013-2073?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2013-2073

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(4)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2013-2073?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(4)

Related CVEs(same CWE)