Bug 888750 - dbus-glib: does not limit XML entity expansion
Summary: dbus-glib: does not limit XML entity expansion
Alias: None
Product: Fedora
Classification: Fedora
Component: dbus-glib
Version: 25
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Colin Walters
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: 888729
TreeView+ depends on / blocked
Reported: 2012-12-19 12:09 UTC by Florian Weimer
Modified: 2017-12-12 10:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2017-12-12 10:27:34 UTC
Type: Bug

Attachments (Terms of Use)

Description Florian Weimer 2012-12-19 12:09:21 UTC
In dbus-glib 0.100, dbus/dbus-gloader-expat.c contains this code:

  expat = XML_ParserCreate_MM ("UTF-8", &memsuite, NULL);
  if (expat == NULL)
    g_error ("No memory to create XML parser\n");

  context.parser = parser_new ();
  context.content = g_string_new (NULL);
  XML_SetUserData (expat, &context);
  XML_SetElementHandler (expat,
  XML_SetCharacterDataHandler (expat,
  if (!XML_Parse (expat, str, len, TRUE))

That is, XML entity expansion is not disabled, leading to a denial-of-service issue.  I think the only point where a trust boundary is cross is in the bash auto-completion helper, so this is very minor and probably not worth a security bug.

Adding the following handler using

  XML_SetEntityDeclHandler(expat, EntityDeclHandler);

should be sufficient to address this issue.

// Stop the parser when an entity declaration is encountered.
static void
EntityDeclHandler(void *userData,
		  const XML_Char *entityName, int is_parameter_entity,
		  const XML_Char *value, int value_length,
		  const XML_Char *base, const XML_Char *systemId,
		  const XML_Char *publicId, const XML_Char *notationName)
  XML_StopParser((XML_Parser)userData, XML_FALSE);

Comment 1 Jan Kurik 2015-12-22 11:34:44 UTC
This bug is currently assigned to an unsupported release. If you think this bug is still valid and should remain open, please re-assign it to a supported release (F22, F23) or to rawhide.

Bugs which will be assigned to an unsupported release are going to be closed as EOL (End Of Life) on January 26th, 2016.

Comment 2 Florian Weimer 2016-04-23 15:40:48 UTC
Still present in rawhide.

Comment 3 Jan Kurik 2016-07-26 05:11:50 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 4 Fedora End Of Life 2017-11-16 19:33:08 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2017-12-12 10:27:34 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.