Skip to content
VulniPulse
Sign in
Advisory severityMedium5.3Red Hat Linux

Medium [CVE-2018-14647] Python's elementtree C accelerator failed to initialise Expat's hash salt during initialization

This medium-severity Red Hat Linux advisory covers CVE-2018-14647 affecting Red Hat Ansible Tower 3.4 for RHEL 7, Red Hat Enterprise Linux 7.4 Advanced Update Support, Red Hat Enterprise Linux 7.4 Telco Extended Update Support.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2018-14647 Source published Source updated

VulniPulse record published

CVE-2018-14647
Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features

Summary

Python's elementtree C accelerator failed to initialise Expat's hash salt during initialization. This could make it easy to conduct denial of service attacks against Expat by constructing an XML document that would cause pathological hash collisions in Expat's internal data structures, consuming large amounts CPU and RAM.

The vulnerability exists in Python versions 3.7.0, 3.6.0 through 3.6.6, 3.5.0 through 3.5.6, 3.4.0 through 3.4.9, 2.7.0 through 2.7.15. Red Hat severity: Moderate — CVSS 5.3 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).

Weakness: CWE-909.

Affected products named by the advisory: Red Hat Ansible Tower 3.4 for RHEL 7; Red Hat Enterprise Linux 7.4 Advanced Update Support; Red Hat Enterprise Linux 7.4 Telco Extended Update Support; Red Hat Enterprise Linux 7.4 Update Services for SAP Solutions; and 9 more.

Affected versions
  • 3.7.0
  • 3.6.0
  • 3.6.6
  • 3.5.0
  • 3.5.6
  • 3.4.0
  • 3.4.9
  • 2.7.0
  • 2.7.15

Official advisory · high-confidence parse· fetched 7 days ago·verify at source

Fixed versions
  • ansible-tower-34/ansible-tower-memcached:1.4.15-28
  • ansible-tower-35/ansible-tower-memcached:1.4.15-28
  • ansible-tower-37/ansible-tower-memcached-rhel7:1.4.15-28
  • python-0:2.7.5-86.el7
  • python-0:2.7.5-63.el7_4
  • python-0:2.7.5-74.el7_5
  • python-0:2.7.5-83.el7_6
  • python27-python-0:2.7.16-4.el6
  • python27-python-jinja2-0:2.6-12.el6
  • rh-python36-python-0:3.6.9-2.el6
  • python27-python-0:2.7.16-4.el7
  • python27-python-jinja2-0:2.6-15.el7
  • rh-python36-python-0:3.6.9-2.el7
  • RHBA-2020:0547
  • RHSA-2019:2030
  • RHSA-2020:1346
  • RHSA-2020:1268
  • RHSA-2020:1462
  • RHSA-2019:1260
  • RHSA-2019:3725

Official advisory · high-confidence parse· fetched 7 days ago·verify at source

Mitigation

Upgrade to a fixed release: ansible-tower-34/ansible-tower-memcached:1.4.15-28, ansible-tower-35/ansible-tower-memcached:1.4.15-28, ansible-tower-37/ansible-tower-memcached-rhel7:1.4.15-28, python-0:2.7.5-86.el7, python-0:2.7.5-63.el7_4, python-0:2.7.5-74.el7_5. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 7 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.