CVE-2019-13346
published 2019-07-17CVE-2019-13346: In MyT 1.5.1, the User[username] parameter has XSS.
PriorityP336medium6.1CVSS 3.0
AVNACLPRNUIRSCCLILAN
EXPLOIT
EPSS
2.19%
80.2th percentile
In MyT 1.5.1, the User[username] parameter has XSS.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| myt_project | myt | — | — |
CVSS provenance
nvdv3.06.1MEDIUMCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:N/I:P/A:N
CVEs like this are exactly what “Exploited This Week” covers.
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.
No detection rules found.
Bugzilla
CVE-2018-13347 mercurial: Buffer underflow in mpatch.c:mpatch_apply()
bugzilla·2018-06-22·CVSS 7.5
CVE-2018-13347 [HIGH] CVE-2018-13347 mercurial: Buffer underflow in mpatch.c:mpatch_apply()
CVE-2018-13347 mercurial: Buffer underflow in mpatch.c:mpatch_apply()
Mercurial before version 4.6.1 is vulnerable to a buffer underflow in mpatch.c:mpatch_apply().
Upstream Changelog:
https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.6.1_.282018-06-06.29
Upstream Patch:
https://www.mercurial-scm.org/repo/hg/rev/1acfc35d478c
Discussion:
Created mercurial tracking bugs for this issue:
Affects: fedora-all [bug 1594088]
---
This is related to CVE-2018-13346: this issue is writing before the output buffer, where the other reads past the end of input. In mercurial 2.6.2, it is present in the apply() function.
---
This issue has been addressed in the following products:
Red Hat Enterprise Linux 7
Via RHSA-2019:2276 https://access.redhat.com/errata/RHSA-2019:2276
---
This b
Bugzilla
CVE-2018-13346 mercurial: Missing check for fragment start position in mpatch.c:mpatch_apply()
bugzilla·2018-06-22·CVSS 7.5
CVE-2018-13346 [HIGH] CVE-2018-13346 mercurial: Missing check for fragment start position in mpatch.c:mpatch_apply()
CVE-2018-13346 mercurial: Missing check for fragment start position in mpatch.c:mpatch_apply()
Mercurial before version 4.6.1 has a missing check for fragment start position in mpatch.c:mpatch_apply()
Upstream Changelog:
https://www.mercurial-scm.org/wiki/WhatsNew#Mercurial_4.6.1_.282018-06-06.29
Upstream Patch:
https://www.mercurial-scm.org/repo/hg/rev/faa924469635
Discussion:
This is related to CVE-2018-13347: this issue is reading past the end of input where the other writes before the output buffer. In mercurial 2.6.2, it is present in the apply() function.
---
Created mercurial tracking bugs for this issue:
Affects: fedora-all [bug 1594088]
---
This issue has been addressed in the following products:
Red Hat Enterprise Linux 7
Via RHSA-2019:2276 https://access.redhat.co
2019-07-17
Published