Skip to content

Added patched_version to 1 (katello) existing advisory - #1275

Closed
jasnow wants to merge 3 commits into
rubysec:masterfrom
jasnow:oct-26a-advs
Closed

jasnow wants to merge 3 commits into
rubysec:masterfrom
jasnow:oct-26a-advs

Conversation

@jasnow

@jasnow jasnow commented Oct 26, 2026

Copy link
Copy Markdown
Member

Added patched_version to 1 (katello) existing advisory

NOTE: After much research and contacting the project, I now have the patched_version for this advisory.

@jasnow
jasnow requested a review from simi October 26, 2026 15:25
Comment thread gems/katello/CVE-2018-14623.yml Resolved

@lzap lzap left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you.

@ianballou ianballou left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 to the changes here looking back at the history as a Katello maintainer.

Clarified information regarding the 3.4.5.58 release and its status.
malformed SQL query to the backend database, which will leak internal IDs.

This is issue is related to an incomplete fix for CVE-2016-3072
(Patched in 2.4.3 on June 13, 2016). Version 3.10 (3.10.0 was

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here is 3.10 mentioned, but later patched is >= 3.5.0 🤔 .

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does the note section answer your question?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lzap and @ianballou - Can you answer @simi question/comment?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since I have not gotten an answer to the 3.5 vs 3.10 question, I am going to cancel PR.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The answer is indeed in the notes section below: this issue was patched in Katello 3.5.0 and above.

3.5.0 commit: Katello/katello@3a7b130

Original 3.6.0.rc1 commit which was cherry-picked back to 3.5.0: Katello/katello@2e39aff

@jasnow jasnow closed this Oct 29, 2026
@lzap

lzap commented Nov 3, 2026

Copy link
Copy Markdown

Guys, frankly I am confused what are we doing in here. We were pulled into some process of reviewing old advisories (?) and asked to clear some things out of nowhere which we did. I do not need to explain how things are in FOSS security, we are being hammered by inquiries and reports the same way as you guys do. A one-week turnaround for a non-urgent case is perfectly fine if you ask me.

I would prefer that the GHSA advisory was corrected first before I moved forward.

As much as I would love to help, I have no idea what your expectation was. I do not have the context, I wish I could help.

@jasnow

jasnow commented Nov 3, 2026

Copy link
Copy Markdown
Member Author

I am going to delete my previous comment. I am sorry.

@simi

simi commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

@jasnow your comment is ok. @lzap we're not authority to decide and triage on the advisories. We do just mirror the authorities.

@jasnow

jasnow commented Nov 4, 2026

Copy link
Copy Markdown
Member Author

Fight copilot with above advisory. Decided to fix grammer 1st.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants