Skip to content
OpenAdvisories
High SUSE-SU-2020:0790-1 1 CVE

Security update for python-cffi, python-cryptography, python-xattr

Published Mar 25, 2020 · Updated Feb 4, 2026

Summary

This update for python-cffi, python-cryptography and python-xattr fixes the following issues:

Security issue fixed:

- CVE-2018-10903: Fixed GCM tag forgery via truncated tag in finalize_with_tag API (bsc#1101820).

Non-security issues fixed:

python-cffi was updated to 1.11.2 (bsc#1138748, jsc#ECO-1256, jsc#PM-1598):

- fixed a build failure on i586 (bsc#1111657)
- Salt was unable to highstate in snapshot 20171129 (bsc#1070737)

- Update pytest in spec to add c directory tests in addition to
testing directory.

Update to 1.11.1:

* Fix tests, remove deprecated C API usage
* Fix (hack) for 3.6.0/3.6.1/3.6.2 giving incompatible binary
extensions (cpython issue #29943)
* Fix for 3.7.0a1+

Update to 1.11.0:

* Support the modern standard types char16_t and char32_t. These
work like wchar_t: they represent one unicode character, or when
used as charN_t * or charN_t[] they represent a unicode string.
The difference with wchar_t is that they have a known, fixed
size. They should work at all places that used to work with
wchar_t (please report an issue if I missed something). Note
that with set_source(), you need to make sure that these types
are actually defined by the C source you provide (if used in
cdef()).
* Support the C99 types float _Complex and double _Complex. Note
that libffi doesn't support them, which means that in the ABI
mode you still cannot call C functions that take complex
numbers directly as arguments or return type.
* Fixed a rare race condition when creating multiple FFI instances
from multiple threads. (Note that you aren't meant to create
many FFI instances: in inline mode, you should write
ffi = cffi.FFI() at module level just after import cffi; and in
out-of-line mode you don't instantiate FFI explicitly at all.)
* Windows: using callbacks can be messy because the CFFI internal
error messages show up to stderr-but stderr goes nowhere in many
applications. This makes it particularly hard to get started
with the embedding mode. (Once you get started, you can at least
use @ffi.def_extern(onerror=...) and send the error logs where
it makes sense for your application, or record them in log
files, and so on.) So what is new in CFFI is that now, on
Windows CFFI will try to open a non-modal MessageBox (in addition
to sending raw messages to stderr). The MessageBox is only
visible if the process stays alive: typically, console
applications that crash close immediately, but that is also the
situation where stderr should be visible anyway.
* Progress on support for callbacks in NetBSD.
* Functions returning booleans would in some case still return 0
or 1 instead of False or True. Fixed.
* ffi.gc() now takes an optional third parameter, which gives an
estimate of the size (in bytes) of the object. So far, this is
only used by PyPy, to make the next GC occur more quickly
(issue #320). In the future, this might have an effect on
CPython too (provided the CPython issue 31105 is addressed).
* Add a note to the documentation: the ABI mode gives function
objects that are slower to call than the API mode does. For
some reason it is often thought to be faster. It is not!

Update to 1.10.1:

* Fixed the line numbers reported in case of cdef() errors. Also,
I just noticed, but pycparser always supported the preprocessor
directive # 42 'foo.h' to mean 'from the next line, we're in
file foo.h starting from line 42';, which it puts in the error
messages.

Update to 1.10.0:

Issue #295: use calloc() directly instead of PyObject_Malloc()+memset()
to handle ffi.new() with a default allocator. Speeds up ffi.new(large-array)
where most of the time you never touch most of the array.
* Some OS/X build fixes ('only with Xcode but without CLT';).
* Improve a couple of error messages: when getting mismatched versions of
cffi and its backend; and when calling functions which cannot be called with
libffi because an argument is a struct that is 'too complicated'; (and not
a struct pointer, which always works).
* Add support for some unusual compilers (non-msvc, non-gcc, non-icc, non-clang)
* Implemented the remaining cases for ffi.from_buffer. Now all
buffer/memoryview objects can be passed. The one remaining check is against
passing unicode strings in Python 2. (They support the buffer interface, but
that gives the raw bytes behind the UTF16/UCS4 storage, which is most of the
times not what you expect. In Python 3 this has been fixed and the unicode
strings don't support the memoryview interface any more.)
* The C type _Bool or bool now converts to a Python boolean when reading,
instead of the content of the byte as an integer. The potential
incompatibility here is what occurs if the byte contains a value different
from 0 and 1. Previously, it would just return it; with this change, CFFI
raises an exception in this case. But this case means 'undefined behavior';
in C; if you really have to interface with a library relying on this,
don't use bool in the CFFI side. Also, it is still valid to use a byte
string as initializer for a bool[], but now it must only contain \x00 or
\x01. As an aside, ffi.string() no longer works on bool[] (but it never made
much sense, as this function stops at the first zero).
* ffi.buffer is now the name of cffi's buffer type, and ffi.buffer() works
like before but is the constructor of that type.
* ffi.addressof(lib, 'name') now works also in in-line mode, not only in
out-of-line mode. This is useful for taking the address of global variables.
* Issue #255: cdata objects of a primitive type (integers, floats, char) are
now compared and ordered by value. For example, <cdata 'int' 42> compares
equal to 42 and <cdata 'char' b'A'> compares equal to b'A'. Unlike C,
<cdata 'int' -1> does not compare equal to ffi.cast('unsigned int', -1): it
compares smaller, because -1 < 4294967295.
* PyPy: ffi.new() and ffi.new_allocator()() did not record 'memory pressure

Fixed packages 7

ReleasePackageFixed in
SUSE · SLES 12 SP1 Linux Enterprise Server 12 SP1-LTSS python-cffi 1.11.2-2.19.2
SUSE · SLES 12 SP1 Linux Enterprise Server 12 SP1-LTSS python-cryptography 2.1.4-3.15.5
SUSE · SLES 12 SP1 Linux Enterprise Server 12 SP1-LTSS python-xattr 0.7.5-3.2.1
SUSE · SLES for SAP 12 SP1 Linux Enterprise Server for SAP Applications 12 SP1 python-cffi 1.11.2-2.19.2
SUSE · SLES for SAP 12 SP1 Linux Enterprise Server for SAP Applications 12 SP1 python-cryptography 2.1.4-3.15.5
SUSE · SLES for SAP 12 SP1 Linux Enterprise Server for SAP Applications 12 SP1 python-xattr 0.7.5-3.2.1
SUSE · OpenStack Cloud 6 OpenStack Cloud 6-LTSS python-cryptography 2.1.4-3.15.5

Vulnerabilities 1

References

  • report
    https://bugzilla.suse.com/1055478
  • report
    https://bugzilla.suse.com/1070737
  • report
    https://bugzilla.suse.com/1101820
  • report
    https://bugzilla.suse.com/1111657
  • report
    https://bugzilla.suse.com/1138748
  • report
    https://bugzilla.suse.com/1149792
  • report
    https://bugzilla.suse.com/981848
  • web
    https://www.suse.com/security/cve/CVE-2018-10903