[Bug 1781214] New: CVE-2019-17632 jetty: generation of default unhandled error response content does not escape exception messages in stacktraces included in error output
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1781214
Bug ID: 1781214
Summary: CVE-2019-17632 jetty: generation of default unhandled
error response content does not escape exception
messages in stacktraces included in error output
Product: Security Response
Hardware: All
OS: Linux
Status: NEW
Component: vulnerability
Keywords: Security
Severity: medium
Priority: medium
Assignee: security-response-team(a)redhat.com
Reporter: gsuckevi(a)redhat.com
CC: aboyko(a)redhat.com, aileenc(a)redhat.com,
bkearney(a)redhat.com, chazlett(a)redhat.com,
drieden(a)redhat.com,
eclipse-sig(a)lists.fedoraproject.org,
ggaughan(a)redhat.com, gvarsami(a)redhat.com,
hhorak(a)redhat.com, janstey(a)redhat.com,
java-maint(a)redhat.com,
java-sig-commits(a)lists.fedoraproject.org,
jcoleman(a)redhat.com, jjohnstn(a)redhat.com,
jochrist(a)redhat.com, jorton(a)redhat.com,
jwon(a)redhat.com, kconner(a)redhat.com,
krathod(a)redhat.com, krzysztof.daniel(a)gmail.com,
ldimaggi(a)redhat.com, mat.booth(a)redhat.com,
mizdebsk(a)redhat.com, nwallace(a)redhat.com,
pdrozd(a)redhat.com, pjindal(a)redhat.com,
rwagner(a)redhat.com, sochotni(a)redhat.com,
sthorger(a)redhat.com, tcunning(a)redhat.com,
tkirby(a)redhat.com, tlestach(a)redhat.com
Target Milestone: ---
Classification: Other
In Eclipse Jetty versions 9.4.21.v20190926, 9.4.22.v20191022, and
9.4.23.v20191118, the generation of default unhandled Error response content
(in text/html and text/json Content-Type) does not escape Exception messages in
stacktraces included in error output.
Reference:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=553443
--
You are receiving this mail because:
You are on the CC list for the bug.
4 years, 1 month
[Bug 1793870] After configuring a new system, selecting packages with errors terminates the installation.
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1793870
--- Comment #10 from George R. Goffe <grgoffe(a)yahoo.com> ---
Jaroslav,
Thank you for responding to this bug report, IT IS APPRECIATED!
Maybe there is already an answer to what I'm asking below. I would appreciate
any pointers/hints/tips.
Can you help me to do more of this kind of research myself please? It would
help "us" all if I could narrow down to a specific package causing trouble.
I am not a dnf/yum/rpm expert by ANY stretch of the imagination. What dnf
commands should be issued by me? Perhaps a brief "flow chart"? Are there other
commands? I know this is a big question but it would help me and maybe most of
the other people writing bug reports. Occasionally I run across a package that
is NOT in bugzilla. Who should I notify about that?
Something short and sweet would be GREATLY appreciated by me for sure. I WANT
to write better bug reports.
What do you think?
Best regards and, again, thanks for your help.
George...
--
You are receiving this mail because:
You are on the CC list for the bug.
4 years, 1 month
[Bug 1769139] New: sisu-0.3.4 is available
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1769139
Bug ID: 1769139
Summary: sisu-0.3.4 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: sisu
Keywords: FutureFeature, Triaged
Assignee: stewardship-sig(a)lists.fedoraproject.org
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: decathorpe(a)gmail.com,
eclipse-sig(a)lists.fedoraproject.org,
java-sig-commits(a)lists.fedoraproject.org,
mhroncok(a)redhat.com, mizdebsk(a)redhat.com,
sochotni(a)redhat.com,
stewardship-sig(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Latest upstream release: 0.3.4
Current version/release in rawhide: 0.3.3-8.fc31
URL: http://eclipse.org/sisu
Please consult the package updates policy before you issue an update to a
stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/20407/
--
You are receiving this mail because:
You are on the CC list for the bug.
4 years, 2 months