CVE-2018-7285
published 2018-02-22CVE-2018-7285: A NULL pointer access issue was discovered in Asterisk 15.x through 15.2.1. The RTP support in Asterisk maintains its own registry of dynamic codecs and…
PriorityP340high7.5CVSS 3.0
AVNACLPRNUINSUCNINAH
EPSS
5.24%
91.5th percentile
A NULL pointer access issue was discovered in Asterisk 15.x through 15.2.1. The RTP support in Asterisk maintains its own registry of dynamic codecs and desired payload numbers. While an SDP negotiation may result in a codec using a different payload number, these desired ones are still stored internally. When an RTP packet was received, this registry would be consulted if the payload number was not found in the negotiated SDP. This registry was incorrectly consulted for all packets, even those which are dynamic. If the payload number resulted in a codec of a different type than the RTP stream (for example, the payload number resulted in a video codec but the stream carried audio), a crash could occur if no stream of that type had been negotiated. This was due to the code incorrectly assuming that a stream of that type would always exist.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | asterisk | — | — |
| digium | asterisk | 15.0.0 – 15.2.1 | — |
CVSS provenance
nvdv3.07.5HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:N/A:P
vendor_debian7.5LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-2pjx-4j7g-wf3f: A NULL pointer access issue was discovered in Asterisk 15
ghsa_unreviewed·2022-05-14
CVE-2018-7285 [HIGH] CWE-476 GHSA-2pjx-4j7g-wf3f: A NULL pointer access issue was discovered in Asterisk 15
A NULL pointer access issue was discovered in Asterisk 15.x through 15.2.1. The RTP support in Asterisk maintains its own registry of dynamic codecs and desired payload numbers. While an SDP negotiation may result in a codec using a different payload number, these desired ones are still stored internally. When an RTP packet was received, this registry would be consulted if the payload number was not found in the negotiated SDP. This registry was incorrectly consulted for all packets, even those which are dynamic. If the payload number resulted in a codec of a different type than the RTP stream (for example, the payload number resulted in a video codec but the stream carried audio), a crash could occur if no stream of that type had been negotiated. This was due to the code incorrectly assum
Debian
CVE-2018-7285: asterisk - A NULL pointer access issue was discovered in Asterisk 15.x through 15.2.1. The ...
vendor_debian·2018·CVSS 7.5
CVE-2018-7285 [HIGH] CVE-2018-7285: asterisk - A NULL pointer access issue was discovered in Asterisk 15.x through 15.2.1. The ...
A NULL pointer access issue was discovered in Asterisk 15.x through 15.2.1. The RTP support in Asterisk maintains its own registry of dynamic codecs and desired payload numbers. While an SDP negotiation may result in a codec using a different payload number, these desired ones are still stored internally. When an RTP packet was received, this registry would be consulted if the payload number was not found in the negotiated SDP. This registry was incorrectly consulted for all packets, even those which are dynamic. If the payload number resulted in a codec of a different type than the RTP stream (for example, the payload number resulted in a video codec but the stream carried audio), a crash could occur if no stream of that type had been negotiated. This was due to the code incorrectly assum
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2018-7285 asterisk: NULL Pointer Dereference in RTP [fedora-all]
bugzilla·2018-02-22·CVSS 7.5
CVE-2018-7285 [HIGH] CVE-2018-7285 asterisk: NULL Pointer Dereference in RTP [fedora-all]
CVE-2018-7285 asterisk: NULL Pointer Dereference in RTP [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fedor
Bugzilla
CVE-2018-7285 asterisk: NULL Pointer Dereference in RTP [epel-6]
bugzilla·2018-02-22·CVSS 7.5
CVE-2018-7285 [HIGH] CVE-2018-7285 asterisk: NULL Pointer Dereference in RTP [epel-6]
CVE-2018-7285 asterisk: NULL Pointer Dereference in RTP [epel-6]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-6.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following template to for the 'fedpkg update' re
Bugzilla
CVE-2018-7285 asterisk: NULL Pointer Dereference in RTP
bugzilla·2018-02-22·CVSS 7.5
CVE-2018-7285 [HIGH] CVE-2018-7285 asterisk: NULL Pointer Dereference in RTP
CVE-2018-7285 asterisk: NULL Pointer Dereference in RTP
A NULL pointer access issue was discovered in Asterisk 15.x through 15.2.1. The RTP support in Asterisk maintains its own registry of dynamic codecs and desired payload numbers. While an SDP negotiation may result in a codec using a different payload number, these desired ones are still stored internally. When an RTP packet was received, this registry would be consulted if the payload number was not found in the negotiated SDP. This registry was incorrectly consulted for all packets, even those which are dynamic. If the payload number resulted in a codec of a different type than the RTP stream (for example, the payload number resulted in a video codec but the stream carried audio), a crash could occur if no stream of that type had be
2018-02-22
Published