security update in Fedora 22 for python-pymongo

Status: obsolete


  • Upstream 3.0.3
  • Fix CVE-2013-7440 (#1231231 #1231232)


  • Upstream 3.0.3
  • Fix CVE-2013-7440 (#1231231 #1231232)


  • Upstream 3.0.3
  • Fix CVE-2013-7440 (#1231231 #1231232)


  • Upstream 3.0.3
  • Fix CVE-2013-7440 (#1231231 #1231232)


  • Upstream 3.0.3
  • Fix CVE-2013-7440 (#1231231 #1231232)

Comments 16

This update has been submitted for testing by hguemar.

This update has been pushed to testing.

This update has reached 7 days in testing and can be pushed to stable now if the maintainer wishes

Please do not push this update out to stable! pymongo version 3 is not backwards compatible and will break its dependent packages! Also, the CVE this addresses is extremely low impact and is highly unlikely to happen in the real world as CAs do not issue certificates like this. If we want to fix the CVE, the correct thing to do is to backport a patch, not to raise the version in a way that breaks dependencies.

karma: -1

This update has been unpushed.

This update has been submitted for testing by hguemar.

@rbarlow: come with concrete examples where this update breaks package.

@rbarlow: come with concrete examples where this update breaks any package. Openstack packages require v3.

This update breaks Pulp, which depends on python-pymongo through python-mongoengine:


Also, the CVE's impact is listed as low and taking advantage of it is listed as complex. These evaluations were made by the secteam.

karma: -1

Furthermore, the backwards incompatibility of this change is well documented here and is extensive:


As observed by rbarlow, this would break potentially a lot of projects; anyone who uses pymongo in fedora.

karma: -1

Per the update policy, under the "Philosophy" section,

"Releases of the Fedora distribution are like releases of the individual packages that compose it. A major version number reflects a more-or-less stable set of features and functionality. As a result, we should avoid major updates of packages within a stable release. Updates should aim to fix bugs, and not introduce features, particularly when those features would materially affect the user or developer experience. The update rate for any given release should drop off over time, approaching zero near release end-of-life; since updates are primarily bugfixes, fewer and fewer should be needed over time."


This is a major version update of the package, breaking backwards compatibility with the previous major version. I suggest finding an alternate solution.

It is already noted here that this will break functionality for one package (Pulp)

karma: -1

This update has been submitted for testing by hguemar.

pulp is not in F22

This is inappropriate. The update policy does not say that it only applies for dependencies that are in Fedora - you are NOT to make backwards incompatible changes. Many projects depend on the distribution to be stable. Do not push this change again.

karma: -1

Add Comment & Feedback

Please login to add feedback.

Content Type
Test Gating
Submitted by
Update Type
Update Severity
stable threshold: 1
unstable threshold: -3
Autopush (karma)
Autopush (time)
submitted 4 years ago
in testing 4 years ago

Related Bugs 3

00 #1210043 Mongoengine require pymongo 2.7.1
00 #1231231 CVE-2013-7440 CVE-2013-2099 python-pymongo: various flaws [fedora-all]
00 #1231232 CVE-2013-7440 CVE-2013-2099 python-pymongo: various flaws [epel-all]

Automated Test Results