Skip to content

Commit 8bb768c

Browse files
committed
Update
Signed-off-by: A.Arnold <[email protected]>
1 parent f89623c commit 8bb768c

File tree

2 files changed

+11
-11
lines changed

2 files changed

+11
-11
lines changed

docs/topics/mta-rn-known-issues-7-0-3.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ When the Application Inventory has to list many applications, the page loads slo
1515

1616
.Failure to run analysis on a directory of multiple applications
1717

18-
{ProductShortName} 7.0.2 and 7.0.3 fails to run analysis on a directory of multiple applications. The cause of this failure is caused as the analyzer is expecting a `pom.xml` file in the root directory. link:https://issues.redhat.com/browse/MTA-2765[(MTA-2765)]
18+
{ProductShortName} 7.0.2 and 7.0.3 fails to run analysis on a directory of multiple applications. The cause of this failure is that the analyzer is expecting a `pom.xml` file in the root directory. link:https://issues.redhat.com/browse/MTA-2765[(MTA-2765)]
1919

2020

2121
For a complete list of all known issues in this release, see the list of link:https://issues.redhat.com/issues/?filter=12434259[Known Issues in Jira].

docs/topics/mta-rn-resolved-issues-7-0-3.adoc

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -38,15 +38,15 @@ A flaw was found in Adobe CSS Tools. Operation input validation may result in a
3838

3939
For more details, see link:https://access.redhat.com/security/cve/cve-2023-26364[(CVE-2023-26364)].
4040

41-
.CVE-2023-45287: Golang: `crypto/tls`: Timing Side Channel Attack in an RSA-Based TLS Key exchanges
41+
.CVE-2023-45287: Golang: `crypto/tls`: Timing Side Channel Attack in an RSA-Based TLS Key exchanges
4242

4343
A flaw was found in the Golang `crypto/tls` standard library. In versions before 1.20, the package was vulnerable to a Timing side-channel attack by observing the time it took for RSA-based Transport Layer Security (TLS) key exchanges, which was not constant. The flaw allowed for potential timing attacks, where the removal of `PKCS#1` padding could have leaked and potentially exposed session key bits.
4444

4545
For more details, see link:https://access.redhat.com/security/cve/cve-2023-45287[(CVE2023-45287)].
4646

4747
.CVE-2023-39326: Golang: `net/http/internal`: denial of service (DoS) caused by resource consumption from HTTP requests
4848

49-
A flaw was found in the Golang `net/http/internal` package that could cause a malicious HTTP sender to cause a receiver reading from a request or response body to read many more bytes from the network than are in the body.  This flaw could cause the receiver to fail to read the response, possibly leading to a denial of service (DoS).
49+
A flaw was found in the Golang `net/http/internal` package that could cause a malicious HTTP sender to cause a receiver reading from a request or response body to read many more bytes from the network than are in the body. This flaw could cause the receiver to fail to read the response, possibly leading to a denial of service (DoS).
5050

5151
For more details, see link:https://access.redhat.com/security/cve/cve-2023-39326[(CVE-2023-39326)].
5252

@@ -58,27 +58,27 @@ For more details, see link:https://access.redhat.com/security/cve/cve-2023-48631
5858

5959
.CVE-2023-26159: `follow-redirects` package: Improper Input Validation caused by the improper handling of URLs by the `url.parse()` function 
6060

61-
An Improper Input Validation flaw was found in the `follow-redirects` package, versions before 1.15.4. due to the improper handling of URLs by the `url.parse()` function. This flaw could be exploited by manipulating the hostname when the new `URL()` throws an error, leading to a misinterpretation and potential redirection of traffic to a malicious site.
61+
An Improper Input Validation flaw was found in the `follow-redirects` package, in versions before 1.15.4. due to the improper handling of URLs by the `url.parse()` function. This flaw could be exploited by manipulating the hostname when the new `URL()` throws an error, leading to a misinterpretation and potential redirection of traffic to a malicious site.
6262

6363
For more details, see link:https://access.redhat.com/security/cve/cve-2023-26159[(CVE-2023-26159)].
6464

6565
.CVE-2024-24786: A flaw was found in Golang's protobuf module, where the unmarshal function can enter an infinite loop
66-
66+
6767
A flaw was found in the `protojson.Unmarshal` function that could cause the function to enter an infinite loop when unmarshaling certain forms of invalid JSON messages. This condition could occur when unmarshaling into a message that contained a `google.protobuf.Any` value, or when the `UnmarshalOptions.DiscardUnknown` option was set in a JSON-formatted message.
68-
68+
6969
For more details, see link:https://access.redhat.com/security/cve/CVE-2024-24786[(CVE-2024-24786)].
7070

7171
.CVE-2024-28849: `follow-redirects` package: could cause a possible credential leak
72-
72+
7373
A flaw was found in versions of the `follow-redirects` package before 1.1.5. This flaw occurs when `follow-redirects` handles cross-domain redirects. It fails to clear the `proxy-authentication` header, which may contain credentials, while it clears the authorization header. As a result, this vulnerability could potentially lead to the leak of sensitive credentials. 
74-
74+
7575
For more details, see line:https://access.redhat.com/security/cve/CVE-2024-28849[(CVE-2024-28849)].
7676

77-
.Fixed incorrect assessment status when running an assessment on two questionnaires
77+
.Fixed incorrect assessment status when running an assessment on two questionnaires
7878

79-
In {ProductShortName} 7.0.2, running two questionnaires displayed the `Assessment` status as `Not started` instead of `In progress`. With this update, the problem has been resolved. As a result, the *Assessment* status shows `In progress` after one questionnaire or archetype is started.
79+
In {ProductShortName} 7.0.2, running two questionnaires displayed the `Assessment` status as `Not started` instead of `In progress`. With this update, the problem has been resolved. As a result, the *Assessment* status shows `In progress` after one questionnaire or archetype is started.
8080

81-
* link:https://issues.redhat.com/browse/MTA-2409[(MTA-2409)]
81+
* link:https://issues.redhat.com/browse/MTA-2409[(MTA-2409)]
8282
8383
* link:https://issues.redhat.com/browse/MTA-2410[(MTA-2410)]
8484

0 commit comments

Comments
 (0)